linux-kernel - Re: (subset) [PATCH 1/6] ASoC: dapm: Initialise kcontrol data for mux/demux controls

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: <165599273226.179867.18058864820347037377.b4-ty@kernel.org>
Date:   Thu, 23 Jun 2022 14:58:52 +0100
From:   Mark Brown <broonie@...nel.org>
To:     ckeepax@...nsource.cirrus.com
Cc:     david.rhodes@...rus.com, james.schulman@...rus.com,
        lgirdwood@...il.com, linux-kernel@...r.kernel.org,
        alsa-devel@...a-project.org, patches@...nsource.cirrus.com
Subject: Re: (subset) [PATCH 1/6] ASoC: dapm: Initialise kcontrol data for mux/demux controls

On Thu, 23 Jun 2022 11:51:15 +0100, Charles Keepax wrote:
> DAPM keeps a copy of the current value of mux/demux controls,
> however this value is only initialised in the case of autodisable
> controls. This leads to false notification events when first
> modifying a DAPM kcontrol that has a non-zero default.
> 
> Autodisable controls are left as they are, since they already
> initialise the value, and there would be more work required to
> support autodisable muxes where the first option isn't disabled
> and/or that isn't the default.
> 
> [...]

Applied to

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

Thanks!

[6/6] ASoC: dapm: Move stereo autodisable check
      commit: 4d6c2b46d81765e920007f76185a8d1fb5e41ca3

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