On Thu, 08 Oct 2026 17:38:07 +0700, [email protected] wrote: > ASoC: Fix constraint return value handling > > From: bui duc phuc <[email protected]> > > Hi all, > > snd_pcm_hw_constraint_minmax() and snd_pcm_hw_constraint_integer() > may return positive values on success. However, ASoC only marks the > DAI, link, or component as started or opened when the corresponding > callback returns 0. > > [...]
Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-7.4 Thanks! [01/24] ASoC: amd: acp: Fix .close() being skipped on rollback https://git.kernel.org/broonie/misc/c/2c3400aa9f39 [02/24] ASoC: amd: ps: Fix acp63_pdm_dma_close() being skipped on rollback https://git.kernel.org/broonie/misc/c/172888114dda [03/24] ASoC: amd: ps: Fix acp63_sdw_dma_close() being skipped on rollback https://git.kernel.org/broonie/misc/c/45dd2b22ea89 [04/24] ASoC: amd: raven: Fix acp3x_dma_close() being skipped on rollback https://git.kernel.org/broonie/misc/c/37ceef26df57 [05/24] ASoC: amd: renoir: Fix acp_pdm_dma_close() being skipped on rollback https://git.kernel.org/broonie/misc/c/a92571113ef2 [06/24] ASoC: amd: vangogh: Fix acp5x_dma_close() being skipped on rollback https://git.kernel.org/broonie/misc/c/38559fcd1c51 [07/24] ASoC: amd: yc: Fix acp6x_pdm_dma_close() being skipped on rollback https://git.kernel.org/broonie/misc/c/06654a3ef513 [08/24] ASoC: apple: mca: Ensure the DAI is marked as started on success https://git.kernel.org/broonie/misc/c/4d23ef7515dd [09/24] ASoC: atmel: atmel-pcm-pdc: Fix atmel_pcm_close() being skipped on rollback https://git.kernel.org/broonie/misc/c/50aaca643038 [10/24] ASoC: codecs: cs42l42: Ensure the DAI is marked as started on success https://git.kernel.org/broonie/misc/c/c2a3d0b2be0c [11/24] ASoC: codecs: nau8325: Ensure the DAI is marked as started on success https://git.kernel.org/broonie/misc/c/0634e7b24727 [12/24] ASoC: codecs: nau8540: Ensure the DAI is marked as started on success https://git.kernel.org/broonie/misc/c/1de1fd7c69a3 [13/24] ASoC: codecs: nau8821: Ensure the DAI is marked as started on success https://git.kernel.org/broonie/misc/c/fc5da89a0a8a [14/24] ASoC: codecs: nau8824: Ensure the DAI is marked as started on success https://git.kernel.org/broonie/misc/c/e66285731262 [15/24] ASoC: codecs: nau8825: Ensure the DAI is marked as started on success https://git.kernel.org/broonie/misc/c/552944e3b027 [16/24] ASoC: codecs: wm8580: Ensure the DAI is marked as started on success https://git.kernel.org/broonie/misc/c/b2c81f056c53 [17/24] ASoC: codecs: wm8782: Ensure the DAI is marked as started on success https://git.kernel.org/broonie/misc/c/29f52545ada7 [18/24] ASoC: imx-pcm-rpmsg: Fix imx_rpmsg_pcm_close() being skipped on rollback https://git.kernel.org/broonie/misc/c/85e56c3bbb7e [19/24] ASoC: intel: atom: Fix .shutdown() being skipped on rollback https://git.kernel.org/broonie/misc/c/e3bb57581104 [20/24] ASoC: renesas: fsi: Ensure the component is marked as opened on success https://git.kernel.org/broonie/misc/c/6bba4e5a171c [21/24] ASoC: renesas: msiof: Fix msiof_close() being skipped on rollback https://git.kernel.org/broonie/misc/c/b7c58a55fd9b [22/24] ASoC: renesas: rz-ssi: Ensure the component is marked as opened on success https://git.kernel.org/broonie/misc/c/fd5c45166d65 [23/24] ASoC: rockchip: rk3399_gru_sound: Mark the link as started on success https://git.kernel.org/broonie/misc/c/8a43611c834f [24/24] ASoC: rockchip: rockchip_max98090: Mark the link as started on success https://git.kernel.org/broonie/misc/c/303961c7daf1 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
