linux-kernel - Re: [PATCH v2] ASoC: sof_sdw: Add a quirk for Lenovo laptop using sidecar amps with cs42l43

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: <176962798768.3150276.8077584571829669236.b4-ty@kernel.org>
Date: Wed, 28 Jan 2026 19:19:47 +0000
From: Mark Brown <broonie@...nel.org>
To: Cezary Rojewski <cezary.rojewski@...el.com>, 
 Liam Girdwood <liam.r.girdwood@...ux.intel.com>, 
 Bard Liao <yung-chuan.liao@...ux.intel.com>, 
 Maciej Strozek <mstrozek@...nsource.cirrus.com>
Cc: Peter Ujfalusi <peter.ujfalusi@...ux.intel.com>, 
 Ranjani Sridharan <ranjani.sridharan@...ux.intel.com>, 
 Kai Vehmanen <kai.vehmanen@...ux.intel.com>, 
 Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>, 
 linux-kernel@...r.kernel.org, linux-sound@...r.kernel.org, 
 patches@...nsource.cirrus.com
Subject: Re: [PATCH v2] ASoC: sof_sdw: Add a quirk for Lenovo laptop using
 sidecar amps with cs42l43

On Wed, 28 Jan 2026 09:24:05 +0000, Maciej Strozek wrote:
> Add a quirk for a Lenovo laptop (SSID: 0x17aa3821) to allow using sidecar
> CS35L57 amps with CS42L43 codec.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: sof_sdw: Add a quirk for Lenovo laptop using sidecar amps with cs42l43
      commit: 681ca5c6fadaa268e2fa3cff8609c4c348377be1

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