From: Mark Brown <broonie@kernel.org>
To: David Lechner <dlechner@baylibre.com>
Cc: David Jander <david@protonic.nl>,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] spi: fix finalize message on error return
Date: Fri, 26 Jan 2024 14:35:33 +0000 [thread overview]
Message-ID: <170627973371.36139.11882822858180324422.b4-ty@kernel.org> (raw)
In-Reply-To: <20240125205312.3458541-2-dlechner@baylibre.com>
On Thu, 25 Jan 2024 14:53:09 -0600, David Lechner wrote:
> In __spi_pump_transfer_message(), the message was not finalized in the
> first error return as it is in the other error return paths. Not
> finalizing the message could cause anything waiting on the message to
> complete to hang forever.
>
> This adds the missing call to spi_finalize_current_message().
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] spi: fix finalize message on error return
commit: 8c2ae772fe08e33f3d7a83849e85539320701abd
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
prev parent reply other threads:[~2024-01-26 14:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 20:53 [PATCH] spi: fix finalize message on error return David Lechner
2024-01-26 14:35 ` Mark Brown [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=170627973371.36139.11882822858180324422.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=david@protonic.nl \
--cc=dlechner@baylibre.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.