Re: [PATCH v5 00/12] ASoC: add and use new snd_soc_register_component()

On Thu, 23 Jul 2026 06:34:03 +0000, Kuninori Morimoto wrote:
> ASoC: add and use new snd_soc_register_component()
> 
> Hi
> 
> Current component has component->name. But snd_soc_register_component()
> user can't setup it, because component itself is alloced in that function.
> 
> [...]

Applied to

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

Thanks!

[01/12] ASoC: soc-component: move soc_component_field_shift()
        https://git.kernel.org/broonie/sound/c/23b64e9b9ba2
[02/12] ASoC: soc-component: add snd_soc_component_alloc()
        https://git.kernel.org/broonie/sound/c/de182d84b3a7
[03/12] ASoC: soc-component: add snd_soc_register_component_{c/d}()
        https://git.kernel.org/broonie/sound/c/3e53dc96a007
[04/12] ASoC: soc-component: add snd_soc_component_{set_}name()
        https://git.kernel.org/broonie/sound/c/f6cfdd246c25
[05/12] ASoC: soc-component: add snd_soc_component_{set/to}_priv()
        https://git.kernel.org/broonie/sound/c/d99690513a9a
[06/12] ASoC: intel: avs: use snd_soc_register_component()
        https://git.kernel.org/broonie/sound/c/6105b0c10c57
[07/12] ASoC: intel: avs: probes: use snd_soc_register_component()
        https://git.kernel.org/broonie/sound/c/825521664559
[08/12] ASoC: intel: catpt: pcm: use snd_soc_register_component()
        https://git.kernel.org/broonie/sound/c/c8eaeedcace3
[09/12] ASoC: soc-generic-dmaengine-pcm: use snd_soc_register_component()
        https://git.kernel.org/broonie/sound/c/695cc675f0d5
[10/12] ASoC: soc-topology-test: use snd_soc_register_component()
        https://git.kernel.org/broonie/sound/c/10c062304d2d
[11/12] ASoC: soc-core: makes snd_soc_component_initialize() / snd_soc_add_component() local
        https://git.kernel.org/broonie/sound/c/7050ee33c2db
[12/12] ASoC: soc-core: remove dev from soc_component_initialize()
        https://git.kernel.org/broonie/sound/c/157936199385

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