[0/6] ASoC: soc-pcm: cleanup code

Message

Kuninori Morimoto Dec. 11, 2020, 5:54 a.m. UTC

Hi Mark

These are not so important, but for
soc-pcm cleanup patches.

Kuninori Morimoto (6):
  ASoC: soc-pcm: move dpcm_set_fe_update_state()
  ASoC: soc-pcm: add dpcm_set_be_update_state()
  ASoC: soc-pcm: add soc_pcm_set_dai_params()
  ASoC: soc-pcm: cleanup soc_pcm_apply_symmetry()
  ASoC: soc-pcm: cleanup soc_pcm_params_symmetry()
  ASoC: soc-pcm: setup pcm at one place in soc_new_pcm()

 sound/soc/soc-pcm.c | 231 +++++++++++++++++---------------------------
 1 file changed, 90 insertions(+), 141 deletions(-)

Comments

Mark Brown Jan. 13, 2021, 3:26 p.m. UTC | #1

On 11 Dec 2020 14:54:53 +0900, Kuninori Morimoto wrote:
> These are not so important, but for
> soc-pcm cleanup patches.
> 
> Kuninori Morimoto (6):
>   ASoC: soc-pcm: move dpcm_set_fe_update_state()
>   ASoC: soc-pcm: add dpcm_set_be_update_state()
>   ASoC: soc-pcm: add soc_pcm_set_dai_params()
>   ASoC: soc-pcm: cleanup soc_pcm_apply_symmetry()
>   ASoC: soc-pcm: cleanup soc_pcm_params_symmetry()
>   ASoC: soc-pcm: setup pcm at one place in soc_new_pcm()
> 
> [...]

Applied to

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

Thanks!

[1/6] ASoC: soc-pcm: move dpcm_set_fe_update_state()
      commit: 9c6d7f9346b1526136dc142eb82085737112a3fe
[2/6] ASoC: soc-pcm: add dpcm_set_be_update_state()
      commit: a7e20444ef5e7ab74aec34f34eb0e53024c349e1
[3/6] ASoC: soc-pcm: add soc_pcm_set_dai_params()
      commit: 2805b8bd3e0bdda15b3458ab9818d80f5d5b157f
[4/6] ASoC: soc-pcm: cleanup soc_pcm_apply_symmetry()
      commit: a39748d03cbc7c0a55d217731c7e16a22a2d2bed

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