On Fri, 3 Jun 2022 13:25:08 +0200, Mark Brown wrote: > Currently snd_soc_info_volsw() will set a platform_max based on the limit > the control has if one is not already set. This isn't really great, we > shouldn't be modifying the passed in driver data especially in a path like > this which may not ever be executed or where we may execute other callbacks > before this one. Instead make this function leave the data unchanged, and > clarify things a bit by referring to max rather than platform_max within > the function. platform_max is now applied as a limit after working out the > natural maximum value for the control. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [1/1] ASoC: ops: Don't modify the driver's plaform_max when reading state commit: 30ac49841386f933339817771ec315a34a4c0edd 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
