linux-kernel - Re: [PATCH] spi: tegra114: remove Kconfig dependency on TEGRA20_APB

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: <176417702689.85368.17056171248019245384.b4-ty@kernel.org>
Date: Wed, 26 Nov 2025 17:10:26 +0000
From: Mark Brown <broonie@...nel.org>
To: Thierry Reding <treding@...dia.com>, 
 Gautham Srinivasan <gauthams@...dia.com>, linux-spi@...r.kernel.org, 
 linux-kernel@...r.kernel.org, Francesco Lavra <flavra@...libre.com>
Subject: Re: [PATCH] spi: tegra114: remove Kconfig dependency on
 TEGRA20_APB_DMA

On Wed, 26 Nov 2025 10:50:27 +0100, Francesco Lavra wrote:
> This driver runs also on Tegra SoCs without a Tegra20 APB DMA controller
> (e.g. Tegra234).
> Remove the Kconfig dependency on TEGRA20_APB_DMA; in addition, amend the
> help text to reflect the fact that this driver works on SoCs different from
> Tegra114.
> 
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: tegra114: remove Kconfig dependency on TEGRA20_APB_DMA
      commit: 3dcf44ab56e1d3ca3532083c0d5390b758e45b45

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