[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <168683495795.547441.10667645380315680455.b4-ty@kernel.org>
Date: Thu, 15 Jun 2023 14:15:57 +0100
From: Mark Brown <broonie@...nel.org>
To: Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>,
Alexandre Torgue <alexandre.torgue@...s.st.com>,
Alain Volmat <alain.volmat@...s.st.com>,
Valentin Caron <valentin.caron@...s.st.com>
Cc: linux-spi@...r.kernel.org, devicetree@...r.kernel.org,
linux-stm32@...md-mailman.stormreply.com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 0/4] spi: stm32: add spi device mode
On Thu, 15 Jun 2023 09:58:11 +0200, Valentin Caron wrote:
> STM32 SPI can operate in device mode.
> This series adds this functionnality in spi-stm32 driver.
>
> Since v2:
> - Rename this series: spi device mode
>
> Since v1:
> - Do not add #address-cells and #size-cells in st,stm32-spi.yaml
> - Do not add cs-gpio description in st,stm32-spi.yaml
> - Do not add st,spi-slave-underrun property to handle spi slave underrun
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/4] spi: stm32: renaming of spi_master into spi_controller
commit: 6f486556abe35f2e6684f95241acbc463342d3eb
[2/4] spi: stm32: use dmaengine_terminate_{a}sync instead of _all
commit: 4f2b39dc2d14d4fc55d7a3a140ac07eaa761b701
[3/4] dt-bindings: spi: stm32: disable spi-slave property for stm32f4-f7
commit: e6afe03351ac81fbc4f2b93bf3b356f7b662939d
[4/4] spi: stm32: introduction of stm32h7 SPI device mode support
commit: e40335fcb89acb274d05deffad9225e973278ec9
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