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: <176104663272.21978.4717954267043604617.b4-ty@kernel.org>
Date: Tue, 21 Oct 2025 12:37:12 +0100
From: Mark Brown <broonie@...nel.org>
To: Simon Trimmer <simont@...nsource.cirrus.com>
Cc: linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 patches@...nsource.cirrus.com, yung-chuan.liao@...ux.intel.com
Subject: Re: [PATCH] ASoC: Intel: soc-acpi-intel-ptl-match: Remove cs42l43
 match from sdw link3

On Thu, 16 Oct 2025 11:26:01 +0000, Simon Trimmer wrote:
> Removing this match entry ensures that a PTL system comprising of a
> cs42l43 codec on link3 will use function topologies.
> 
> Previously the behaviour would be use the monolithic topology associated
> with this codec match table entry in preference to function topologies
> and if the system had a number of smart amplifiers then they would not
> be instantiated.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: Intel: soc-acpi-intel-ptl-match: Remove cs42l43 match from sdw link3
      commit: 3bcdbc221d676f871e23da30fd485a76728f55c7

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