Re: [PATCH 0/8] ASoC: Series of loose fixes

From: Mark Brown

Date: Fri Oct 16 2026 - 06:36:10 EST


On Wed, 14 Oct 2026 22:06:00 +0200, Amadeusz Sławiński wrote:
> ASoC: Series of loose fixes
>
> Following current fashion of poking code with LLM to see what issues it
> finds. Some are minor, other more likely to cause some real issues like
> the one with snd_soc_limit_volume() returning positive value, while
> callers do simple if (ret) check.
>
> [...]

Applied to

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

Thanks!

[1/8] ASoC: soc-link: Correct stream stop operations in snd_soc_link_trigger
https://git.kernel.org/broonie/sound/c/7ef99fcfbbac
[2/8] ASoC: ops: Fix return value in snd_soc_limit_volume()
https://git.kernel.org/broonie/sound/c/223ec2a93bec
[3/8] ASoC: soc-topology-test: Check return value of kunit_device_register()
https://git.kernel.org/broonie/sound/c/1641c1ba27ab
[4/8] ASoC: soc-card-test: Check return value of kunit_device_register()
https://git.kernel.org/broonie/sound/c/77dfd98b1642
[5/8] ASoC: soc-ac97: Fix error handling in snd_soc_new_ac97_component()
https://git.kernel.org/broonie/sound/c/fc081cdfc6b3
[6/8] ASoC: soc-ac97: Fix debug message
https://git.kernel.org/broonie/sound/c/9d4bab22932f
[7/8] ASoC: soc-component: Fix return type of snd_soc_pcm_component_pointer()
https://git.kernel.org/broonie/sound/c/9df30adce80d
[8/8] ASoC: soc-dapm: Remove widget from cache on removal
https://git.kernel.org/broonie/sound/c/568406bc832e

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