linux-kernel - Re: [PATCH] ASoC: codecs: wcd938x: use defines for entries in snd_soc_dai

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: <169833313276.133649.3664120134410239820.b4-ty@kernel.org>
Date:   Thu, 26 Oct 2023 16:12:12 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Liam Girdwood <lgirdwood@...il.com>,
        Jaroslav Kysela <perex@...ex.cz>,
        Takashi Iwai <tiwai@...e.com>, alsa-devel@...a-project.org,
        linux-kernel@...r.kernel.org,
        Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Subject: Re: [PATCH] ASoC: codecs: wcd938x: use defines for entries in
 snd_soc_dai_driver array

On Thu, 19 Oct 2023 16:41:08 +0200, Krzysztof Kozlowski wrote:
> snd_soc_dai_driver array in wcd938x driver has two entries whose order
> must match order of wcd938x->sdw_priv array.  The wcd938x_bind() and
> wcd938x_codec_set_sdw_stream() rely on this order.  wcd938x->sdw_priv
> array is indexed by enum with AIF1_PB and AIF1_CAP, so use the same
> defines instead of raw numners for snd_soc_dai_driver array.
> No functional impact.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: codecs: wcd938x: use defines for entries in snd_soc_dai_driver array
      commit: 7618ab524935667699afed76fb83bc9bb38710ec

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