linux-kernel - Re: [PATCH] ASoC: max98373: Removing 0x203E from the volatile reg

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: <165883025392.54936.4365512627715267394.b4-ty@kernel.org>
Date:   Tue, 26 Jul 2022 11:10:53 +0100
From:   Mark Brown <broonie@...nel.org>
To:     tiwai@...e.com, linux-kernel@...r.kernel.org, lgirdwood@...il.com,
        steve@....org, alsa-devel@...a-project.org, perex@...ex.cz,
        ryans.lee@...log.com, Ryan Lee <ryan.lee.analog@...il.com>
Subject: Re: [PATCH] ASoC: max98373: Removing 0x203E from the volatile reg

On Fri, 22 Jul 2022 18:52:20 -0700, Ryan Lee wrote:
> The 0x203E speaker gain register should be non-volatile.
> This register value was not able to be synced because it was marked as
> volatile.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: max98373: Removing 0x203E from the volatile reg
      commit: bd1963d837a082e1083cd396803d3d263a9ef68b

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