Re: [PATCH 0/7] ASoC: core: Create new components in sane state

[Mark Brown]

On Wed, 07 Oct 2026 15:33:46 +0200, Cezary Rojewski wrote:
> ASoC: core: Create new components in sane state
> 
> There is a gap between snd_soc_component_alloc() and
> snd_soc_register_component().  A driver that obtains a component object
> through snd_soc_component_alloc() receives an object in uninitialized
> state.  soc_component_initialize() is the function responsible for
> bringing it into a sane one but it is not accessible by the framework
> users.  Example of the uninitialized members are the lists e.g.:
> comp->dai_list.
> 
> [...]

Applied to

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

Thanks!

[1/7] ASoC: core: Add component constructor
      https://git.kernel.org/broonie/misc/c/0f2bec6921f0
[2/7] ASoC: core: Rename and export soc_component_add()
      https://git.kernel.org/broonie/misc/c/4e2db62172b5
[3/7] ASoC: dmaengine: Switch to snd_snd_component_new()
      https://git.kernel.org/broonie/misc/c/857469990ee1
[4/7] ASoC: topology-test: Switch to snd_snd_component_new()
      https://git.kernel.org/broonie/misc/c/c0e1ffec60ce
[5/7] ASoC: Intel: catpt: Switch to snd_snd_component_new()
      https://git.kernel.org/broonie/misc/c/6cb74a0741da
[6/7] ASoC: Intel: avs: Switch to snd_snd_component_new()
      https://git.kernel.org/broonie/misc/c/d7065004a33a
[7/7] ASoC: core: Remove unused component-register members
      https://git.kernel.org/broonie/misc/c/146caaa16f85

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