On Fri, 16 Oct 2026 11:09:35 +0700, [email protected] wrote: > ASoC: Address remaining PCM constraint issues > > From: bui duc phuc <[email protected]> > > Hi all, > > Since v1 has already been applied, this series provides incremental > changes to address the remaining items from v2: > - Add comments explaining why .open() and .startup() must return 0 > on success to prevent the issue from being reintroduced. > - Add Reviewed-by tags from Vijendar Mukunda and Chancel Liu, > and Acked-by tags from Morimoto-san and Cezary. > - Remove redundant integer constraints already applied > by snd_dmaengine_pcm_open(). > > [...]
Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-7.4 Thanks! [01/11] ASoC: amd: Explain component open return value handling https://git.kernel.org/broonie/sound/c/1ba2cb30eeab [02/11] ASoC: apple: Explain DAI startup return value handling https://git.kernel.org/broonie/sound/c/ec2e1434c7f7 [03/11] ASoC: atmel: Explain component open return value handling https://git.kernel.org/broonie/sound/c/1554ce7a5d99 [04/11] ASoC: codecs: Explain DAI startup return value handling https://git.kernel.org/broonie/sound/c/a6b1f3ccca48 [05/11] ASoC: imx-pcm-rpmsg: Explain component open return value handling https://git.kernel.org/broonie/sound/c/f3e3dbbbbfd6 [06/11] ASoC: intel: atom: Explain DAI startup return value handling https://git.kernel.org/broonie/sound/c/2f8d93394b7f [07/11] ASoC: renesas: msiof: Explain component open return value handling https://git.kernel.org/broonie/sound/c/394f91bd0f7a [08/11] ASoC: renesas: msiof: Remove redundant period constraint https://git.kernel.org/broonie/sound/c/d2f4c848d010 [09/11] ASoC: renesas: rz-ssi: Explain component open return value handling https://git.kernel.org/broonie/sound/c/65850cb2f9ce [10/11] ASoC: renesas: rz-ssi: Remove redundant component open callback https://git.kernel.org/broonie/sound/c/a0b64de6ea7e [11/11] ASoC: rockchip: Explain DAI link startup return value handling https://git.kernel.org/broonie/sound/c/48ed45aa30ce 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
