linux-kernel - Re: [PATCH v3] spi: rockchip: Resolve unbalanced runtime PM / system PM handling

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: <172493426855.31273.9511769608557747574.b4-ty@kernel.org>
Date: Thu, 29 Aug 2024 13:24:28 +0100
From: Mark Brown <broonie@...nel.org>
To: Brian Norris <briannorris@...omium.org>
Cc: Jon Lin <jon.lin@...k-chips.com>, 
 Ondřej Jirman <megi@....cz>, stable@...r.kernel.org, 
 Heiko Stuebner <heiko@...ech.de>, linux-arm-kernel@...ts.infradead.org, 
 linux-kernel@...r.kernel.org, linux-rockchip@...ts.infradead.org, 
 linux-spi@...r.kernel.org, shengfei Xu <xsf@...k-chips.com>
Subject: Re: [PATCH v3] spi: rockchip: Resolve unbalanced runtime PM /
 system PM handling

On Tue, 27 Aug 2024 10:11:16 -0700, Brian Norris wrote:
> Commit e882575efc77 ("spi: rockchip: Suspend and resume the bus during
> NOIRQ_SYSTEM_SLEEP_PM ops") stopped respecting runtime PM status and
> simply disabled clocks unconditionally when suspending the system. This
> causes problems when the device is already runtime suspended when we go
> to sleep -- in which case we double-disable clocks and produce a
> WARNing.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: rockchip: Resolve unbalanced runtime PM / system PM handling
      commit: be721b451affbecc4ba4eaac3b71cdbdcade1b1b

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