linux-kernel - Re: [PATCH] ASoC: nau8325: Revise soc

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: <171208620085.89523.17981494000577046407.b4-ty@kernel.org>
Date: Tue, 02 Apr 2024 20:30:00 +0100
From: Mark Brown <broonie@...nel.org>
To: lgirdwood@...il.com, Seven Lee <wtli@...oton.com>
Cc: perex@...ex.cz, tiwai@...e.com, linux-sound@...r.kernel.org, 
 linux-kernel@...r.kernel.org, YHCHuang@...oton.com, KCHSU0@...oton.com, 
 CTLIN0@...oton.com, SJLIN0@...oton.com, scott6986@...il.com, 
 supercraig0719@...il.com, dardar923@...il.com
Subject: Re: [PATCH] ASoC: nau8325: Revise soc_enum structure definition.

On Mon, 01 Apr 2024 18:47:53 +0800, Seven Lee wrote:
> This patch is modified nau8325_dac_oversampl_enum enumerated.
> Use SOC_VALUE_ENUM instead to hide empty (presumably invalid) options.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: nau8325: Revise soc_enum structure definition.
      commit: 91ebd32eee6cd7714b49ca4463a0f315bc26ce0e

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