public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: linux-spi@vger.kernel.org, robh@kernel.org, krzk+dt@kernel.org,
	 conor+dt@kernel.org, CL Wang <cl634@andestech.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	 tim609@andestech.com
Subject: Re: [PATCH V3 0/3] spi: atcspi200: Add support for Andes ATCSPI200 SPI controller
Date: Thu, 18 Dec 2025 12:06:43 +0000	[thread overview]
Message-ID: <176605960378.141857.4623173953165594324.b4-ty@kernel.org> (raw)
In-Reply-To: <20251215132349.513843-1-cl634@andestech.com>

On Mon, 15 Dec 2025 21:23:46 +0800, CL Wang wrote:
> This series adds support for the Andes ATCSPI200 SPI controller.
> 
> Changes in v3:
>   - Reworked the DT binding to properly describe the compatible fallback
>     relationship, defining "andestech,qilai-spi" as a platform-specific
>     compatible that falls back to the generic "andestech,ae350-spi".
>   - Renamed the DT binding file from 'andestech,qilai-spi.yaml' to
>     'andestech,ae350-spi.yaml' to match the generic fallback compatible.
>   - Updated the 'compatible' property to use a 'oneOf' schema, enforcing
>     the fallback requirement for the specific compatible string.
>   - Updated the MAINTAINERS entry to reflect the renamed DT binding file.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[1/3] dt-bindings: spi: Add support for ATCSPI200 SPI controller
      commit: b2f06783081859b200a853f9682d831b6fc9982d
[2/3] spi: atcspi200: Add ATCSPI200 SPI controller driver
      commit: 34e3815ea4597131d4324a4aa243d2201e672005
[3/3] MAINTAINERS: Add MAINTAINERS entry for the ATCSPI200 SPI controller driver
      commit: 1303c2903889b01d581083ed92e439e7544dd3e5

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


      parent reply	other threads:[~2025-12-18 12:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-15 13:23 [PATCH V3 0/3] spi: atcspi200: Add support for Andes ATCSPI200 SPI controller CL Wang
2025-12-15 13:23 ` [PATCH V3 1/3] dt-bindings: spi: Add support for " CL Wang
2025-12-16 16:37   ` Conor Dooley
2025-12-15 13:23 ` [PATCH V3 2/3] spi: atcspi200: Add ATCSPI200 SPI controller driver CL Wang
2025-12-15 13:23 ` [PATCH V3 3/3] MAINTAINERS: Add MAINTAINERS entry for the " CL Wang
2025-12-18 12:06 ` 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=176605960378.141857.4623173953165594324.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=cl634@andestech.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=tim609@andestech.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