linux-kernel - Re: [PATCH 0/5] ASoC: cs35l56: Add support for new Dell laptops

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: <176908836510.85917.8367911975448640969.b4-ty@kernel.org>
Date: Thu, 22 Jan 2026 13:26:05 +0000
From: Mark Brown <broonie@...nel.org>
To: Richard Fitzgerald <rf@...nsource.cirrus.com>
Cc: linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 patches@...nsource.cirrus.com
Subject: Re: [PATCH 0/5] ASoC: cs35l56: Add support for new Dell laptops

On Wed, 21 Jan 2026 13:22:38 +0000, Richard Fitzgerald wrote:
> On new Dell models the driver must read a UEFI variable to get a
> variant identifier for the audio hardware. Without this, the driver
> cannot know which firmware file to load to the amps.
> 
> Patch #1 and #2 are the new support.
> The other patches are for KUnit testing.
> 
> [...]

Applied to

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

Thanks!

[1/5] ASoC: cs-amp-lib: Support Dell SSIDExV2 UEFI variable
      commit: 00fd40bc7acecf9f41d645aa0b35ddc7fd7679b6
[2/5] ASoC: cs35l56: Use vendor-specific qualifier in firmware file search
      commit: 51b069172a4ef2c6278c64c603a41a7f20329921
[3/5] ASoC: cs-amp-lib-test: Tests for reading SSIDExV2
      commit: d70fa6b569a95e71cc25b86ac3cc221bea541f53
[4/5] ASoC: cs-amp-lib: Add a Kconfig symbol for enabling test hooks
      commit: 3f086a4f277af799467af6c74902000461e60a33
[5/5] ASoC: cs35l56: Add KUnit testing of cs35l56_set_fw_suffix()
      commit: d0ab89951197f0fc509a0cd732d830880e79c2d4

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