public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Rob Herring <robh+dt@kernel.org>,
	 Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	 Conor Dooley <conor+dt@kernel.org>,
	 Alexandre Torgue <alexandre.torgue@foss.st.com>,
	 Alain Volmat <alain.volmat@foss.st.com>,
	 Valentin Caron <valentin.caron@foss.st.com>
Cc: linux-spi@vger.kernel.org, devicetree@vger.kernel.org,
	 linux-stm32@st-md-mailman.stormreply.com,
	 linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/4] spi: stm32: add spi device mode
Date: Thu, 15 Jun 2023 14:15:57 +0100	[thread overview]
Message-ID: <168683495795.547441.10667645380315680455.b4-ty@kernel.org> (raw)
In-Reply-To: <20230615075815.310261-1-valentin.caron@foss.st.com>

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


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      parent reply	other threads:[~2023-06-15 13:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-15  7:58 [PATCH v3 0/4] spi: stm32: add spi device mode Valentin Caron
2023-06-15  7:58 ` [PATCH v3 1/4] spi: stm32: renaming of spi_master into spi_controller Valentin Caron
2023-08-16 15:07   ` Leonard Göhrs
2023-06-15  7:58 ` [PATCH v3 2/4] spi: stm32: use dmaengine_terminate_{a}sync instead of _all Valentin Caron
2023-06-15  7:58 ` [PATCH v3 3/4] dt-bindings: spi: stm32: disable spi-slave property for stm32f4-f7 Valentin Caron
2023-06-15 13:36   ` Krzysztof Kozlowski
2023-06-15 17:38     ` Valentin CARON
2023-06-15 17:40       ` Mark Brown
2023-06-15 20:20       ` Krzysztof Kozlowski
2023-06-15  7:58 ` [PATCH v3 4/4] spi: stm32: introduction of stm32h7 SPI device mode support Valentin Caron
2023-06-15 13:15 ` 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=168683495795.547441.10667645380315680455.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=alain.volmat@foss.st.com \
    --cc=alexandre.torgue@foss.st.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --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=robh+dt@kernel.org \
    --cc=valentin.caron@foss.st.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