Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Simon Trimmer <simont@opensource.cirrus.com>
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
	 patches@opensource.cirrus.com, Vijendar.Mukunda@amd.com,
	 syed.sabakareem@amd.com
Subject: Re: [PATCH 0/4] ASoC: amd: acp: Add ACP7.0 match entries for Cirrus Logic parts
Date: Tue, 03 Feb 2026 12:05:26 +0000	[thread overview]
Message-ID: <177012032678.85387.7873071739767595957.b4-ty@kernel.org> (raw)
In-Reply-To: <cover.1769534442.git.simont@opensource.cirrus.com>

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


      parent reply	other threads:[~2026-02-03 12:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-27 17:34 [PATCH 0/4] ASoC: amd: acp: Add ACP7.0 match entries for Cirrus Logic parts Simon Trimmer
2026-01-27 17:34 ` [PATCH 1/4] ASoC: amd: acp: Sort match table into most specific first Simon Trimmer
2026-01-27 17:34 ` [PATCH 2/4] ASoC: amd: acp: Rename Cirrus Logic component match entries to include link and uid Simon Trimmer
2026-01-27 17:34 ` [PATCH 3/4] ASoC: amd: acp: Sort Cirrus Logic match entries Simon Trimmer
2026-01-27 17:34 ` [PATCH 4/4] ASoC: amd: acp: Add ACP7.0 match entries for Cirrus Logic parts Simon Trimmer
2026-02-03 12:05 ` Mark Brown [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=177012032678.85387.7873071739767595957.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=Vijendar.Mukunda@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=patches@opensource.cirrus.com \
    --cc=simont@opensource.cirrus.com \
    --cc=syed.sabakareem@amd.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox