Message ID | 20220201155629.120510-1-broonie@kernel.org (mailing list archive) |
---|---|
Headers | show |
Series | ASoC: ops: Fix stereo change notifications | expand |
On Tue, 1 Feb 2022 15:56:25 +0000, Mark Brown wrote: > The event generation coverage I just wrote shows that the generic ASoC > ops fail to generate events for stereo controls when only the first > channel is changed, we just return the status for the second channel and > discard that for the first. > > Mark Brown (4): > ASoC: ops: Fix stereo change notifications in snd_soc_put_volsw() > ASoC: ops: Fix stereo change notifications in snd_soc_put_volsw_sx() > ASoC: ops: Fix stereo change notifications in > snd_soc_put_volsw_range() > ASoC: ops: Fix stereo change notifications in snd_soc_put_xr_sx() > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-linus Thanks! [1/4] ASoC: ops: Fix stereo change notifications in snd_soc_put_volsw() commit: 564778d7b1ea465f9487eedeece7527a033549c5 [2/4] ASoC: ops: Fix stereo change notifications in snd_soc_put_volsw_sx() commit: 7f3d90a3519680dfa23e750f80bfdefc0f5eda4a [3/4] ASoC: ops: Fix stereo change notifications in snd_soc_put_volsw_range() commit: 650204ded3703b5817bd4b6a77fa47d333c4f902 [4/4] ASoC: ops: Fix stereo change notifications in snd_soc_put_xr_sx() commit: 2b7c46369f09c358164d31d17e5695185403185e 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