linux-kernel - Re: [PATCH v3 0/3] Axiado AX3000 SoC SPI DB controller driver

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: <176831496192.83859.8720209174414217917.b4-ty@kernel.org>
Date: Tue, 13 Jan 2026 14:36:01 +0000
From: Mark Brown <broonie@...nel.org>
To: Tzu-Hao Wei <twei@...ado.com>, Swark Yang <syang@...ado.com>, 
 Prasad Bolisetty <pbolisetty@...ado.com>, Rob Herring <robh@...nel.org>, 
 Krzysztof Kozlowski <krzk+dt@...nel.org>, 
 Conor Dooley <conor+dt@...nel.org>, Harshit Shah <hshah@...ado.com>, 
 Vladimir Moravcevic <vmoravcevic@...ado.com>
Cc: linux-spi@...r.kernel.org, devicetree@...r.kernel.org, 
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 0/3] Axiado AX3000 SoC SPI DB controller driver

On Wed, 07 Jan 2026 23:44:36 -0800, Vladimir Moravcevic wrote:
> This updated patch series address the review comments from the v2 submission.
> It introduces new SPI controller driver for Axiado AX3000 SoC and its evaluation board.
> 
> The SPI controller provides:
> - Full-duplex and half-duplex transfer support
> - Configurable clock polarity and phase
> - Interrupt-driven
> 
> [...]

Applied to

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

Thanks!

[1/3] dt-bindings: spi: axiado,ax3000-spi: Add binding for Axiado SPI DB controller
      commit: 7b122b1eb627059bd331d5119124a2da5e142c01
[2/3] spi: axiado: Add driver for Axiado SPI DB controller
      commit: e75a6b00ad7962a7ed1c9c777e9ab1eb29043ec8
[3/3] MAINTAINERS: Add entries for the Axiado SPI DB controller
      commit: db4371d13f82fb12463fe053f4864980a2af2106

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