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]
Message-Id: <176772528289.317829.14666571712516939644.b4-ty@kernel.org>
Date: Tue, 06 Jan 2026 18:48:02 +0000
From: Mark Brown <broonie@...nel.org>
To: Srinivas Kandagatla <srini@...nel.org>, Johan Hovold <johan@...nel.org>
Cc: Liam Girdwood <lgirdwood@...il.com>, linux-sound@...r.kernel.org, 
 linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/4] ASoC: codecs: wsa88xx: fix codec initialisation

On Fri, 02 Jan 2026 12:14:09 +0100, Johan Hovold wrote:
> The soundwire update_status() callback may be called multiple times with
> the same ATTACHED status but initialisation should only be done when
> transitioning from UNATTACHED to ATTACHED.
> 
> This series fixes the Qualcomm wsa88xx codec drivers that do unnecessary
> reinitialisation or potentially fail to initialise at all.
> 
> [...]

Applied to

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

Thanks!

[1/4] ASoC: codecs: wsa883x: fix unnecessary initialisation
      commit: 49aadf830eb048134d33ad7329d92ecff45d8dbb
[2/4] ASoC: codecs: wsa881x: fix unnecessary initialisation
      commit: 29d71b8a5a40708b3eed9ba4953bfc2312c9c776
[3/4] ASoC: codecs: wsa884x: fix codec initialisation
      commit: 120f3e6ff76209ee2f62a64e5e7e9d70274df42b
[4/4] ASoC: codecs: wsa883x: suppress variant printk
      commit: 46a16d89d097ac2c93b63382a37d60aa7f21dc71

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


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ