linux-kernel - Re: [PATCH 1/4] ASoC: wm5102: Fix event generation for output compensation

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]

Date:   Wed, 29 Jun 2022 14:05:59 +0100
From:   Mark Brown <broonie@...nel.org>
To:     ckeepax@...nsource.cirrus.com
Cc:     alsa-devel@...a-project.org, lgirdwood@...il.com,
        linux-kernel@...r.kernel.org, patches@...nsource.cirrus.com
Subject: Re: [PATCH 1/4] ASoC: wm5102: Fix event generation for output compensation

On Tue, 28 Jun 2022 16:34:06 +0100, Charles Keepax wrote:
> The output compensation controls always returns zero regardless of if
> the control value was updated. This results in missing notifications
> to user-space of the control change. Update the handling to return 1
> when the value is changed.
> 
> 

Applied to

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

Thanks!

[1/4] ASoC: wm5102: Fix event generation for output compensation
      commit: cb41d454b2478a98c831f14e656a34c21418e241
[2/4] ASoC: wm8998: Fix event generation for input mux
      commit: a83f511909217a1c2b971a509c992b6327bb18e7
[3/4] ASoC: cs47l92: Fix event generation for OUT1 demux
      commit: 2d81cca17329dece1c4f37d1de271bc967439327
[4/4] ASoC: arizona: Update arizona_aif_cfg_changed to use RX_BCLK_RATE
      commit: 6f04f1bfe9a4adf750c816f6094878222e496d0e

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