[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <176605960378.141857.4623173953165594324.b4-ty@kernel.org>
Date: Thu, 18 Dec 2025 12:06:43 +0000
From: Mark Brown <broonie@...nel.org>
To: linux-spi@...r.kernel.org, robh@...nel.org, krzk+dt@...nel.org,
conor+dt@...nel.org, CL Wang <cl634@...estech.com>
Cc: devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
tim609@...estech.com
Subject: Re: [PATCH V3 0/3] spi: atcspi200: Add support for Andes ATCSPI200
SPI controller
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
Powered by blists - more mailing lists