linux-kernel - Re: [PATCH v5 0/3] support for amlogic the new SPI IP

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <175339209371.157729.12033130863447409564.b4-ty@kernel.org>
Date: Thu, 24 Jul 2025 22:21:33 +0100
From: Mark Brown <broonie@...nel.org>
To: Sunny Luo <sunny.luo@...ogic.com>, Rob Herring <robh@...nel.org>, 
 Krzysztof Kozlowski <krzk+dt@...nel.org>, 
 Conor Dooley <conor+dt@...nel.org>, Xianwei Zhao <xianwei.zhao@...ogic.com>
Cc: linux-amlogic@...ts.infradead.org, linux-spi@...r.kernel.org, 
 devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, 
 Conor Dooley <conor.dooley@...rochip.com>
Subject: Re: [PATCH v5 0/3] support for amlogic the new SPI IP

On Fri, 18 Jul 2025 09:52:15 +0800, Xianwei Zhao wrote:
> Introduced support for the new SPI IP (SPISG). The SPISG is
> a communication-oriented SPI controller from Amlogic,supporting
> three operation modes: PIO, block DMA, and scatter-gather DMA.
> 
> Add the drivers and device tree bindings corresponding to the SPISG.
> 
> 
> [...]

Applied to

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

Thanks!

[1/3] spi: dt-bindings: Add binding document of Amlogic SPISG controller
      commit: 78d35a20783941c8ba5cf912349728c6e1bee84b
[2/3] spi: Add Amlogic SPISG driver
      commit: cef9991e04aed3305c61c392e880f6e01a0c2ea4
[3/3] MAINTAINERS: Add an entry for Amlogic spi driver
      commit: 0ef2a9779e9decee52a85bc393309b3e068a74a6

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