linux-kernel - Re: [PATCH] ASoC: codecs: va-macro: fix revision checking

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: <176182254570.10093.9949103757388632951.b4-ty@kernel.org>
Date: Thu, 30 Oct 2025 11:09:05 +0000
From: Mark Brown <broonie@...nel.org>
To: Srinivas Kandagatla <srinivas.kandagatla@....qualcomm.com>
Cc: perex@...ex.cz, tiwai@...e.com, srini@...nel.org, 
 linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 linux-arm-msm@...r.kernel.org, konrad.dybcio@....qualcomm.com, 
 prasad.kumpatla@....qualcomm.com
Subject: Re: [PATCH] ASoC: codecs: va-macro: fix revision checking

On Wed, 29 Oct 2025 14:43:35 +0000, Srinivas Kandagatla wrote:
> The revision rework patch seems to have reversed the bit positions for
> macro presence in core_id_1 register.
> 
> This broken RB1 and Arduino UnoQ audio.
> Fix these bit positions to correctly reflect the register definition.
> 
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: codecs: va-macro: fix revision checking
      commit: 20bcda681f8597e86070a4b3b12d1e4f541865d3

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