linux-kernel - Re: [PATCH] spi: st: fix PM macros to use CONFIG_PM instead of CONFIG_PM

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: <175580071592.121070.12973016680658012702.b4-ty@kernel.org>
Date: Thu, 21 Aug 2025 19:25:15 +0100
From: Mark Brown <broonie@...nel.org>
To: Geert Uytterhoeven <geert@...ux-m68k.org>, 
 Raphael Gallais-Pou <rgallaispou@...il.com>
Cc: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] spi: st: fix PM macros to use CONFIG_PM instead of
 CONFIG_PM_SLEEP

On Wed, 20 Aug 2025 20:03:10 +0200, Raphael Gallais-Pou wrote:
> pm_sleep_ptr() depends on CONFIG_PM_SLEEP while pm_ptr() depends on
> CONFIG_PM.  Since ST SSC4 implements runtime PM it makes sense using
> pm_ptr() here.
> 
> For the same reason replace PM macros that use CONFIG_PM.  Doing so
> prevents from using __maybe_unused attribute of runtime PM functions.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: st: fix PM macros to use CONFIG_PM instead of CONFIG_PM_SLEEP
      commit: 7c7cda81159b1abe7d50bcef2ccc6f662e225c8b

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