linux-kernel - Re: [PATCH] spi: SPI_AXIADO should depend on ARCH

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: <176957137951.1524024.776031797757604394.b4-ty@kernel.org>
Date: Wed, 28 Jan 2026 03:36:19 +0000
From: Mark Brown <broonie@...nel.org>
To: Vladimir Moravcevic <vmoravcevic@...ado.com>, 
 Prasad Bolisetty <pbolisetty@...ado.com>, 
 Geert Uytterhoeven <geert+renesas@...der.be>
Cc: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] spi: SPI_AXIADO should depend on ARCH_AXIADO

On Tue, 27 Jan 2026 20:08:31 +0100, Geert Uytterhoeven wrote:
> The Axiado DB-H SPI controller is only present on Axiado AX3000 SoCs.
> Hence add a dependency on ARCH_AXIADO, to prevent asking the user about
> this driver when configuring a kernel without Axiado SoC Family support.
> 
> 

Applied to

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

Thanks!

[1/1] spi: SPI_AXIADO should depend on ARCH_AXIADO
      commit: e540be7d56d740144b1bd6f220b61ffe2f3830d4

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