Re: [PATCH 0/6] ASoC: soc-acpi-intel-matchs: use function topology by default

On Thu, 23 Jul 2026 15:05:15 +0800, Bard Liao wrote:
> ASoC: soc-acpi-intel-matchs: use function topology by default
> 
> With commit c84179a1d36b ("ASoC: Intel: sof_sdw: append dai type to dai
> link name unconditionally"), function topology can apply to all
> SoundWire codec configurations. Set .get_function_tplg_files callback to
> use function topology by default. If any required function topology can
> not be found in the file system, it will fallback to use the monolithic
> topology.
> 
> [...]

Applied to

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

Thanks!

[1/6] ASoC: Intel: add snd_soc_acpi_intel_rt712_vb_no_function_topology machine check function
      https://git.kernel.org/broonie/sound/c/c626e2e0b279
[2/6] ASoC: soc-acpi-intel-ptl-match: add machine check for machines can't use function topology
      https://git.kernel.org/broonie/sound/c/168e80166596
[3/6] ASoC: soc-acpi-intel-ptl-match: use function topology by default
      https://git.kernel.org/broonie/sound/c/3b4cfca660b5
[4/6] ASoC: soc-acpi-intel-lnl-match: use function topology by default
      https://git.kernel.org/broonie/sound/c/c4611d4c476d
[5/6] ASoC: soc-acpi-intel-arl-match: use function topology by default
      https://git.kernel.org/broonie/sound/c/3f17f5a1e2b2
[6/6] ASoC: soc-acpi-intel-mtl-match: use function topology by default
      https://git.kernel.org/broonie/sound/c/da1e707bc258

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