linux-kernel - Re: [PATCH 0/4] ASoC: codecs: wcd93xx: Drop enums for chipid values (minor cleanup)

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <175087318970.198995.7502242059805940864.b4-ty@kernel.org>
Date: Wed, 25 Jun 2025 18:39:49 +0100
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, 
 Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Cc: linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/4] ASoC: codecs: wcd93xx: Drop enums for chipid
 values (minor cleanup)

On Mon, 16 Jun 2025 13:54:07 +0200, Krzysztof Kozlowski wrote:
> Minor cleanup while preparing for adding WCD9378 support: do not use
> enum for values which are not an enumeration.
> 
> Best regards,
> Krzysztof
> 

Applied to

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

Thanks!

[1/4] ASoC: codecs: wcd937x: Use simple defines for chipid register value
      commit: 2f6ff1e615cd4f8a86c9d0e4e778db9ae44d5481
[2/4] ASoC: codecs: wcd938x: Use simple defines for chipid register value
      commit: 100877df34b00257c9ed6d279b06b3ed1da5e2c1
[3/4] ASoC: codecs: wcd939x: Use simple defines for chipid register value
      commit: 5d3ccd356e2ce510bdbd4b0c389f2fe3deb41a45
[4/4] ASoC: codecs: wcd939x: Add defines for major/minor version decoding
      commit: a48352921f0b15b1f7eff83f5b5613d6ae2350d3

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