linux-kernel - Re: [PATCH] ASoC: core: remove setting platform

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <166074665821.210979.14610893486592798976.b4-ty@kernel.org>
Date:   Wed, 17 Aug 2022 15:30:58 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
Cc:     lgirdwood@...il.com, alsa-devel@...a-project.org,
        linux-kernel@...r.kernel.org, perex@...ex.cz, tiwai@...e.com
Subject: Re: [PATCH] ASoC: core: remove setting platform_max in kcontrol macros

On Tue, 16 Aug 2022 18:21:29 +0100, Srinivas Kandagatla wrote:
> platform_max should not be set by the driver, its intended for machine drivers
> or DT to override the max value for platform specific reasons.
> 
> So remove setting this from Kcontrol macros.
> 
> Setting this to max in these macros would limit the range when min
> value is less then zero.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: core: remove setting platform_max in kcontrol macros
      commit: 26bdcc4ba12351642cd94339aa6996f96434dd47

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