linux-kernel - Re: [PATCH 0/4] drivers: spi: st: use pm_ptr and remove __maybe

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: <176772394559.309686.18171199857083341971.b4-ty@kernel.org>
Date: Tue, 06 Jan 2026 18:25:45 +0000
From: Mark Brown <broonie@...nel.org>
To: Maxime Coquelin <mcoquelin.stm32@...il.com>, 
 Alexandre Torgue <alexandre.torgue@...s.st.com>, 
 Alain Volmat <alain.volmat@...s.st.com>
Cc: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org, 
 linux-stm32@...md-mailman.stormreply.com, 
 linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 0/4] drivers: spi: st: use pm_ptr and remove
 __maybe_unused

On Tue, 06 Jan 2026 13:14:16 +0100, Alain Volmat wrote:
> Update ST related SPI drivers in order to remove the __maybe_unused
> statements on pm related functions thanks to the usage of pm_ptr.
> 
> 

Applied to

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

Thanks!

[1/4] drivers: spi: st: remove __maybe_unused for suspend/resume
      commit: d4469e4ee5da0a93eabfcb89a8c6ecdf7cf1e9be
[2/4] drivers: spi: stm32-ospi: avoid __maybe_unused and use pm_ptr
      commit: 2a2d7187f5a7238582c2bbd4a6da7595c20e55a9
[3/4] drivers: spi: stm32-qspi: avoid __maybe_unused and use pm_ptr
      commit: 10a6d7507791a667fe1d327056ac3f72934cc7de
[4/4] drivers: spi: stm32: avoid __maybe_unused and use pm_ptr
      commit: 75d208bddcca55ec31481420fbb4d6c9703ba195

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