linux-kernel - Re: [PATCH v1 1/1] spi: cadence-xspi: Replace ACPI specifics by agnostic APIs

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: <176580716744.161463.9153763964021295249.b4-ty@kernel.org>
Date: Mon, 15 Dec 2025 22:59:27 +0900
From: Mark Brown <broonie@...nel.org>
To: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org, 
 Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Subject: Re: [PATCH v1 1/1] spi: cadence-xspi: Replace ACPI specifics by
 agnostic APIs

On Sat, 29 Nov 2025 16:17:39 +0100, Andy Shevchenko wrote:
> Replace ACPI specific calls to get device property with the agnostic one.
> The code looses the direct dependency to the ACPI APIs and get cleaner.
> This doesn't change functionality.
> 
> While at it, drop now unneeded acpi.h.
> 
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: cadence-xspi: Replace ACPI specifics by agnostic APIs
      commit: 6f9e4740e8591176eb90bb1dae95bbbb5c7d789e

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