linux-kernel - Re: [PATCH v2 0/2] ASoC: ak4458 & ak5558: disable regulator if error

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: <176485345924.29556.8568992403267479103.b4-ty@kernel.org>
Date: Thu, 04 Dec 2025 13:04:19 +0000
From: Mark Brown <broonie@...nel.org>
To: lgirdwood@...il.com, perex@...ex.cz, tiwai@...e.com, 
 andriy.shevchenko@...ux.intel.com, 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 v2 0/2] ASoC: ak4458 & ak5558: disable regulator if
 error

On Wed, 03 Dec 2025 18:05:27 +0800, Shengjiu Wang wrote:
> Disable regulator when error happens to balance the reference count.
> 
> changes in v2:
> - set regmap to cache only also.
> 
> Shengjiu Wang (2):
>   ASoC: ak4458: Disable regulator when error happens
>   ASoC: ak5558: Disable regulator when error happens
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: ak4458: Disable regulator when error happens
      commit: ae585fabb9713a43e358cf606451386757225c95
[2/2] ASoC: ak5558: Disable regulator when error happens
      commit: 1f8f726a2a29c28f65b30880335a1610c5e63594

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