linux-kernel - Re: [PATCH RFC 0/2] ASoC: codecs: pm4125: Two minor fixes for potential issues

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: <176314000498.179998.13753639237348930413.b4-ty@kernel.org>
Date: Fri, 14 Nov 2025 17:06:44 +0000
From: Mark Brown <broonie@...nel.org>
To: Srinivas Kandagatla <srini@...nel.org>, 
 Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, Alexey Klimov <alexey.klimov@...aro.org>, 
 Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Cc: Srinivas Kandagatla <srinivas.kandagatla@....qualcomm.com>, 
 linux-sound@...r.kernel.org, linux-arm-msm@...r.kernel.org, 
 linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH RFC 0/2] ASoC: codecs: pm4125: Two minor fixes for
 potential issues

On Thu, 23 Oct 2025 11:02:49 +0200, Krzysztof Kozlowski wrote:
> I marked these as fixes, but the issue is not likely to trigger in
> normal conditions.
> 
> Not tested on hardware, please kindly provide tested-by, the best with
> some probe bind/unbind cycle.
> 
> Best regards,
> Krzysztof
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: codecs: pm4125: Fix potential conflict when probing two devices
      commit: fd94857a934cbe613353810a024c84d54826ead3
[2/2] ASoC: codecs: pm4125: Remove irq_chip on component unbind
      commit: e65b871c9b5af9265aefc5b8cd34993586d93aab

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