linux-kernel - Re: [PATCH] ASoC: codecs: rt5665: Fix some error handling paths in rt5665

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: <174344335604.156807.17437043302594599763.b4-ty@kernel.org>
Date: Mon, 31 Mar 2025 18:49:16 +0100
From: Mark Brown <broonie@...nel.org>
To: Oder Chiou <oder_chiou@...ltek.com>, 
 Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, Bard Liao <bardliao@...ltek.com>, 
 Christophe JAILLET <christophe.jaillet@...adoo.fr>
Cc: linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org, 
 linux-sound@...r.kernel.org
Subject: Re: [PATCH] ASoC: codecs: rt5665: Fix some error handling paths in
 rt5665_probe()

On Sat, 22 Mar 2025 08:45:49 +0100, Christophe JAILLET wrote:
> Should an error occur after a successful regulator_bulk_enable() call,
> regulator_bulk_disable() should be called, as already done in the remove
> function.
> 
> Instead of adding an error handling path in the probe, switch from
> devm_regulator_bulk_get() to devm_regulator_bulk_get_enable() and
> simplify the remove function and some other places accordingly.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: codecs: rt5665: Fix some error handling paths in rt5665_probe()
      commit: 1ebd4944266e86a7ce274f197847f5a6399651e8

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