linux-kernel - Re: [PATCH 0/3] ASoC: es8323: power and mixer controls cleanup and revision

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: <175563281428.270039.6714574776717315231.b4-ty@kernel.org>
Date: Tue, 19 Aug 2025 20:46:54 +0100
From: Mark Brown <broonie@...nel.org>
To: lgirdwood@...il.com, perex@...ex.cz, tiwai@...e.com, 
 Shimrra Shai <shimrrashai@...il.com>
Cc: linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 0/3] ASoC: es8323: power and mixer controls cleanup and
 revision

On Thu, 14 Aug 2025 23:20:20 -0500, Shimrra Shai wrote:
> This is a revision of a previous patch submission of mine wherein one
> part was accepted and one part was not. It was originally phrased for
> a particular device using the ES8323 CODEC, and I was advised to make
> the mixer controls user-selectable so it was not tied to the needs of
> any specific device. This submission brings the DAC and mixer controls
> for basic audio playback on this CODEC into line with the DAPM
> infrastructure and enables their operation through the standard mixer
> interface.
> 
> [...]

Applied to

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

Thanks!

[1/3] ASoC: es8323: remove DAC enablement write from es8323_probe
      commit: 33bc29123d26f7caa7d11f139e153e39104afc6c
[2/3] ASoC: es8323: add proper left/right mixer controls via DAPM
      commit: 7e39ca4056d11fef6b90aedd9eeeb3e070d3ce9f
[3/3] ASoC: es8323: enable DAPM power widgets for playback DAC
      (no commit info)

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