linux-kernel - Re: [PATCH] ASoC: da7219: Correct the process of setting up Gnd switch in AAD

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: <169756266208.1643819.1484143250686725896.b4-ty@kernel.org>
Date:   Tue, 17 Oct 2023 18:11:02 +0100
From:   Mark Brown <broonie@...nel.org>
To:     David Rau <David.Rau.opensource@...renesas.com>
Cc:     support.opensource@...semi.com, lgirdwood@...il.com,
        perex@...ex.cz, tiwai@...e.com, alsa-devel@...a-project.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: da7219: Correct the process of setting up Gnd
 switch in AAD

On Tue, 17 Oct 2023 10:12:58 +0800, David Rau wrote:
> Enable Gnd switch to improve stability when Jack insert event
> occurs, and then disable Gnd switch after Jack type detection
> is finished.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: da7219: Correct the process of setting up Gnd switch in AAD
      commit: e8ecffd9962fe051d53a0761921b26d653b3df6b

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