From: Mark Brown <broonie@kernel.org>
To: Alain Volmat <alain.volmat@st.com>, amelie.delaunay@st.com
Cc: linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
alexandre.torgue@st.com, mcoquelin.stm32@gmail.com,
fabrice.gasnier@st.com, linux-arm-kernel@lists.infradead.org,
linux-spi@vger.kernel.org
Subject: Re: [PATCH 0/5] spi: stm32: various driver fixes
Date: Mon, 10 Aug 2020 19:58:01 +0100 [thread overview]
Message-ID: <159708588098.21609.3669591483839193551.b4-ty@kernel.org> (raw)
In-Reply-To: <1596806485-3810-1-git-send-email-alain.volmat@st.com>
On Fri, 7 Aug 2020 15:21:20 +0200, Alain Volmat wrote:
> This serie is a reduced version of the serie
> [spi: stm32: various driver enhancements] previously sent.
>
> Alain Volmat (1):
> spi: stm32: always perform registers configuration prior to transfer
>
> Amelie Delaunay (3):
> spi: stm32: fix fifo threshold level in case of short transfer
> spi: stm32: fix stm32_spi_prepare_mbr in case of odd clk_rate
> spi: stm32: fixes suspend/resume management
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/4] spi: stm32h7: fix race condition at end of transfer
commit: 135dd873d3c76d812ae64c668adef3f2c59ed27f
[2/4] spi: stm32: fix stm32_spi_prepare_mbr in case of odd clk_rate
commit: 9cc61973bf9385b19ff5dda4a2a7e265fcba85e4
[3/4] spi: stm32: fixes suspend/resume management
commit: db96bf976a4fc65439be0b4524c0d41427d98814
[4/4] spi: stm32: always perform registers configuration prior to transfer
commit: 60ccb3515fc61a0124c70aa37317f75b67560024
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:[~2020-08-10 18:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 13:21 Alain Volmat
2020-08-07 13:21 ` [PATCH 1/5] spi: stm32h7: fix race condition at end of transfer Alain Volmat
2020-08-07 13:21 ` [PATCH 2/5] spi: stm32: fix fifo threshold level in case of short transfer Alain Volmat
2020-08-07 13:27 ` Mark Brown
2020-08-07 13:21 ` [PATCH 3/5] spi: stm32: fix stm32_spi_prepare_mbr in case of odd clk_rate Alain Volmat
2020-08-07 13:21 ` [PATCH 4/5] spi: stm32: fixes suspend/resume management Alain Volmat
2020-08-07 13:21 ` [PATCH 5/5] spi: stm32: always perform registers configuration prior to transfer Alain Volmat
2020-08-10 18:58 ` 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=159708588098.21609.3669591483839193551.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=alain.volmat@st.com \
--cc=alexandre.torgue@st.com \
--cc=amelie.delaunay@st.com \
--cc=fabrice.gasnier@st.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®