linux-kernel - Re: [PATCH] ASoC: es8328: Propagate error codes from regmap updates

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: <176856975159.65310.2733962757462297163.b4-ty@kernel.org>
Date: Fri, 16 Jan 2026 13:22:31 +0000
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, 
 Hsieh Hung-En <hungen3108@...il.com>
Cc: Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>, 
 linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: es8328: Propagate error codes from regmap
 updates

On Fri, 16 Jan 2026 00:13:59 +0800, Hsieh Hung-En wrote:
> In es8328_hw_params(), the return value of
> snd_soc_component_update_bits() was ignored. This could lead to silent
> failures where the hardware is left in an inconsistent state if a
> regmap write fails.
> 
> Check the return value of regmap updates and propagate any errors back
> to the ALSA core. Return 0 on success to match the DAI ops convention.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: es8328: Propagate error codes from regmap updates
      commit: 4711b292b440a8404833df0e0ba96dad86600a84

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