linux-kernel - Re: [PATCH v4 0/3] ASoC: codecs: lpass: add support for v2.5 rx macro

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]

Date: Sat, 15 Jun 2024 21:16:52 +0100
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, Banajit Goswami <bgoswami@...cinc.com>, 
 Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
Cc: neil.armstrong@...aro.org, linux-arm-msm@...r.kernel.org, 
 krzysztof.kozlowski@...aro.org, linux-sound@...r.kernel.org, 
 linux-kernel@...r.kernel.org, alsa-devel@...a-project.org
Subject: Re: [PATCH v4 0/3] ASoC: codecs: lpass: add support for v2.5 rx
 macro

On Thu, 13 Jun 2024 11:49:30 +0100, Srinivas Kandagatla wrote:
> This patchset adds support to reading codec version and also adds
> support for v2.5 codec version in rx macro.
> 
> LPASS 2.5 and up versions have changes in some of the rx blocks which
> are required to get headset functional correctly.
> 
> Tested this on SM8450, X13s and x1e80100 crd.
> 
> [...]

Applied to

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

Thanks!

[1/3] ASoC: codecs: lpass-macro: add helpers to get codec version
      commit: 378918d5918116b95300dd7f03913a1d0841f223
[2/3] ASoC: codec: lpass-rx-macro: prepare driver to accomdate new codec versions
      commit: dbacef05898d65f586fb9b90ba367e6bf898d68d
[3/3] ASoC: codec: lpass-rx-macro: add support for 2.5 codec version
      commit: 432e5074f805d0f976c7430af376a0dd07f1c6d7

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