linux-kernel - Re: [PATCH 0/2] ASoC: cs35l56: Set correct upper volume limit

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 for Android: free password hash cracker in your pocket

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

Message-Id: <172002729026.88190.11217430564421888436.b4-ty@kernel.org>
Date: Wed, 03 Jul 2024 18:21:30 +0100
From: Mark Brown <broonie@...nel.org>
To: Richard Fitzgerald <rf@...nsource.cirrus.com>
Cc: linux-kernel@...r.kernel.org, patches@...nsource.cirrus.com, 
 alsa-devel@...a-project.org, linux-sound@...r.kernel.org
Subject: Re: [PATCH 0/2] ASoC: cs35l56: Set correct upper volume limit

On Wed, 03 Jul 2024 10:55:15 +0100, Richard Fitzgerald wrote:
> These two commits set the upper limit of the Speaker Volume control
> to +12dB instead of +100dB.
> 
> This should have been a simple 1-line change to the #define in the
> header file, but only the HDA cs35l56 driver is using this define.
> The ASoC cs35l56 driver was using hardcoded numbers instead of the
> header defines.
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: cs35l56: Use header defines for Speaker Volume control definition
      commit: c66995ae403073212f5ba60d2079003866c6e130
[2/2] ASoC: cs35l56: Limit Speaker Volume to +12dB maximum
      commit: 244389bd42870640c4b5ef672a360da329b579ed

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