linux-kernel - Re: [PATCH v1 1/1] spi: nxp-fspi: Propagate fwnode in ACPI case as well

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: <176427846537.166028.5032840309459905636.b4-ty@kernel.org>
Date: Thu, 27 Nov 2025 21:21:05 +0000
From: Mark Brown <broonie@...nel.org>
To: Haibo Chen <haibo.chen@....com>, linux-spi@...r.kernel.org, 
 imx@...ts.linux.dev, linux-kernel@...r.kernel.org, 
 Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: Han Xu <han.xu@....com>, Yogesh Gaur <yogeshgaur.83@...il.com>
Subject: Re: [PATCH v1 1/1] spi: nxp-fspi: Propagate fwnode in ACPI case as
 well

On Wed, 26 Nov 2025 21:25:01 +0100, Andy Shevchenko wrote:
> Propagate fwnode of the ACPI device to the SPI controller Linux device.
> Currently only OF case propagates fwnode to the controller.
> 
> While at it, replace several calls to dev_fwnode() with a single one
> cached in a local variable, and unify checks for fwnode type by using
> is_*_node() APIs.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: nxp-fspi: Propagate fwnode in ACPI case as well
      commit: 40ad64ac25bb736740f895d99a4aebbda9b80991

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