linux-kernel - Re: [PATCH 0/2] ASoC: codecs: warn on unknown codec version

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: <172318883316.484675.7690867442520809785.b4-ty@kernel.org>
Date: Fri, 09 Aug 2024 08:33:53 +0100
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, 
 Srinivas Kandagatla <srinivas.kandagatla@...aro.org>, 
 Banajit Goswami <bgoswami@...cinc.com>, 
 Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
Cc: linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 alsa-devel@...a-project.org, linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH 0/2] ASoC: codecs: warn on unknown codec version

On Sat, 03 Aug 2024 13:41:39 +0300, Dmitry Baryshkov wrote:
> While debugging broken audio issues on some of Qualcomm platforms I
> stumbled upon the kernel not providing the actual error information.
> It prints an error from the wsa_macro driver, but the actual issue is in
> the VA macro driver. Add error message to point to the actual error
> location.
> 
> va_macro 3370000.codec: Unknown VA Codec version, ID: 00 / 0f / 00
> wsa_macro 3240000.codec: Unsupported Codec version (0)
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: codecs: lpass-macro: fix version strings returned for 1.x codecs
      commit: 49f6202ce991742f451fc724f03d0c17460d06cd
[2/2] ASoC: codecs: lpass-va-macro: warn on unknown version
      commit: a9a7a2d80790d06cd32c535e2e7b10f72ce592e7

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