[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <162608669456.4543.12090183716809322116.b4-ty@kernel.org>
Date: Mon, 12 Jul 2021 11:45:39 +0100
From: Mark Brown <broonie@...nel.org>
To: amelie.delaunay@...s.st.com,
Alain Volmat <alain.volmat@...s.st.com>
Cc: Mark Brown <broonie@...nel.org>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-spi@...r.kernel.org,
linux-stm32@...md-mailman.stormreply.com,
alexandre.torgue@...s.st.com, mcoquelin.stm32@...il.com,
fabrice.gasnier@...s.st.com
Subject: Re: (subset) [PATCH v2 0/7] spi: stm32: various fixes & cleanup
On Wed, 7 Jul 2021 10:26:59 +0200, Alain Volmat wrote:
> This series contains fixes & cleanup mainly regarding fifo
> and the way end of transfer triggered, when used with or
> without DMA.
> An additional patch cleans up the pm_runtime calls and another
> one enables the autosuspend.
>
> v2: - split pm_runtime fix patch into two
> - correct revert commit subject line
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[2/7] spi: stm32: enable pm_runtime autosuspend
commit: 9d5354145104cf392568a948c5ce2cb97f373fd7
[3/7] spi: stm32h7: fix full duplex irq handler handling
(no commit info)
[4/7] spi: stm32: Revert "properly handle 0 byte transfer"
commit: 70526e0b7601792bf546044fff92c368112f1d3f
[5/7] spi: stm32h7: rework rx fifo read function
commit: d87a5d64b5037cfedd7eb47d785b5c159ace8d9b
[6/7] spi: stm32h7: don't wait for EOT and flush fifo on disable
commit: dc6620c31326bc50fa22fd8900a9f995d0a04bc1
[7/7] spi: stm32: finalize message either on dma callback or EOT
commit: 7ceb0b8a3ceddc36ae4ef1cba6c25a0e28ed65fc
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
Powered by blists - more mailing lists