linux-kernel - Re: [PATCH] ASoC: mediatek: Fix double pm_runtime

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: <176156862550.24382.7526074553836824881.b4-ty@kernel.org>
Date: Mon, 27 Oct 2025 12:37:05 +0000
From: Mark Brown <broonie@...nel.org>
To: Haotian Zhang <vulab@...as.ac.cn>
Cc: lgirdwood@...il.com, perex@...ex.cz, tiwai@...e.com, 
 matthias.bgg@...il.com, angelogioacchino.delregno@...labora.com, 
 linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 linux-arm-kernel@...ts.infradead.org, linux-mediatek@...ts.infradead.org
Subject: Re: [PATCH] ASoC: mediatek: Fix double pm_runtime_disable in
 remove functions

On Tue, 21 Oct 2025 01:04:40 +0800, Haotian Zhang wrote:
> Both mt8195-afe-pcm and mt8365-afe-pcm drivers use devm_pm_runtime_enable()
> in probe function, which automatically calls pm_runtime_disable() on device
> removal via devres mechanism. However, the remove callbacks explicitly call
> pm_runtime_disable() again, resulting in double pm_runtime_disable() calls.
> 
> Fix by removing the redundant pm_runtime_disable() calls from remove
> functions, letting the devres framework handle it automatically.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: mediatek: Fix double pm_runtime_disable in remove functions
      commit: 79a6f2da168543c0431ade57428f673c19c5b72f

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