linux-kernel - Re: [PATCH v1] ASoC: codecs: rt5670: use SOC_VALUE_ENUM_SINGLE

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: <176061852987.55339.14552254610555727404.b4-ty@kernel.org>
Date: Thu, 16 Oct 2025 13:42:09 +0100
From: Mark Brown <broonie@...nel.org>
To: oder_chiou@...ltek.com, lgirdwood@...il.com, perex@...ex.cz, 
 tiwai@...e.com, Alex Tran <alex.t.tran@...il.com>
Cc: linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1] ASoC: codecs: rt5670: use
 SOC_VALUE_ENUM_SINGLE_DECL for DAC2 L/R MX-1B

On Sun, 28 Sep 2025 17:46:25 -0700, Alex Tran wrote:
> DAC2 L/R source selection fields (MX-1B [6:4] and [2:0]) contain non
> contiguous values due to reserved bits documented in datasheet (page 66):
> <https://www.elinfor.com/pdf/RealtekMicroelectronics/ALC5670-VB-
> RealtekMicroelectronics.pdf>
> 
> Switch from SOC_ENUM_SINGLE_DECL to SOC_VALUE_ENUM_SINGLE_DECL
> to handle discrete values.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: codecs: rt5670: use SOC_VALUE_ENUM_SINGLE_DECL for DAC2 L/R MX-1B
      commit: 6621b0f118d500092f5f3d72ddddb22aeeb3c3a0

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