[PATCH v3 0/8] ASoC: soc-pcm: cleanup each functions
Mark Brown
broonie at kernel.org
Fri Mar 12 21:23:49 CET 2021
On 09 Mar 2021 10:07:24 +0900, Kuninori Morimoto wrote:
> These are v2 of soc-pcm cleanup patches.
> These has no relationship to each other.
>
> My 1 concern is [3/8] patch. I think it is no problem,
> but I'm not 100% sure why current code was such code.
> Pierre-Louis / Liam might about something.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/8] ASoC: soc-pcm: check DAI activity under soc_pcm_apply_symmetry()
commit: f8fc9ec56f341c2a7aa263049340b11c9956962f
[2/8] ASoC: soc-pcm: add soc_cpu/codec_dai_name() macro
commit: 6fb8944cd2892e018d13955c2d51579a30744904
[3/8] ASoC: soc-pcm: direct copy at snd_soc_set_runtime_hwparams()
commit: 56e749ba756fdc2eff332b8eadda8fca231ad782
[4/8] ASoC: soc-pcm: add soc_pcm_update_symmetry()
commit: 68cbc557375e22e921c9fd007dfcb35faeff4908
[5/8] ASoC: soc-pcm: add soc_hw_sanity_check()
commit: c393281a3c1cb252735c46efbf8501a3782f9afa
[6/8] ASoC: soc-pcm: fixup dpcm_be_dai_startup() user count
commit: 1db19c151819dea7a0dc4d888250d25abaf229ca
[7/8] ASoC: soc-pcm: remove unneeded !rtd->dai_link check
commit: 20048a9a4070d046a868c3be3b4f7bdc139cc203
[8/8] ASoC: soc-pcm: share DPCM BE DAI stop operation
commit: 531590bb40f827fb3c4398148af0797f95bbaee2
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
More information about the Alsa-devel
mailing list