linux-kernel - Re: [PATCH] ASoC: ak4458: remove the reset operation in probe and remove

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: <176608186982.237766.387212395125669292.b4-ty@kernel.org>
Date: Thu, 18 Dec 2025 18:17:49 +0000
From: Mark Brown <broonie@...nel.org>
To: lgirdwood@...il.com, perex@...ex.cz, tiwai@...e.com, 
 p.zabel@...gutronix.de, kuninori.morimoto.gx@...esas.com, 
 nichen@...as.ac.cn, linux-sound@...r.kernel.org, 
 linux-kernel@...r.kernel.org, ckeepax@...nsource.cirrus.com, 
 Shengjiu Wang <shengjiu.wang@....com>
Subject: Re: [PATCH] ASoC: ak4458: remove the reset operation in probe and
 remove

On Tue, 16 Dec 2025 15:02:01 +0800, Shengjiu Wang wrote:
> The reset_control handler has the reference count for usage, as there is
> reset operation in runtime suspend and resume, then reset operation in
> probe() would cause the reference count of reset not balanced.
> 
> Previously add reset operation in probe and remove is to fix the compile
> issue with !CONFIG_PM, as the driver has been update to use
> RUNTIME_PM_OPS(), so that change can be reverted.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: ak4458: remove the reset operation in probe and remove
      commit: 00b960a83c764208b0623089eb70af3685e3906f

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