linux-kernel - Re: [PATCH 0/4] ASoC: amd: acp: Add ACP7.0 match entries for Cirrus Logic parts

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: <177012032678.85387.7873071739767595957.b4-ty@kernel.org>
Date: Tue, 03 Feb 2026 12:05:26 +0000
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, Vijendar.Mukunda@....com, 
 syed.sabakareem@....com
Subject: Re: [PATCH 0/4] ASoC: amd: acp: Add ACP7.0 match entries for
 Cirrus Logic parts

On Tue, 27 Jan 2026 17:34:45 +0000, Simon Trimmer wrote:
> This patch series adds a number of ACP7.0 match table entries that are
> being used in customer products.
> 
> Some of the configurations are very similar so the series begins with
> renaming and sorting the existing structures so that the end result is
> easier to manage.
> 
> [...]

Applied to

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

Thanks!

[1/4] ASoC: amd: acp: Sort match table into most specific first
      commit: 9ba734901cfd67d1b2101cce803a62d422e81b67
[2/4] ASoC: amd: acp: Rename Cirrus Logic component match entries to include link and uid
      commit: 5eb3fc48d37157fd83315bcbb5693269fc497fb7
[3/4] ASoC: amd: acp: Sort Cirrus Logic match entries
      commit: 3de9cf4782492b19c9d8bdac309462027e18ab43
[4/4] ASoC: amd: acp: Add ACP7.0 match entries for Cirrus Logic parts
      commit: ddd9bf2212ab80bb90fa986cd987c671de53bd44

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