[PATCH v2 0/1] ASoC: dpcm: acquire dpcm_lock in dpcm_do_trigger()

Kuninori Morimoto kuninori.morimoto.gx at renesas.com
Thu Dec 3 08:02:09 CET 2020


Hi Gyeongtaek

Thank you for your help

> I tried to find out some change from the history.
> However, I saw that dpcm_lock never be held in dpcm_be_dai_trigger() from the beginning.
> So, I just fixed some miss from the commit comment and resend.
> If you have another suggestion or request, just let me know.

OK, thanks.
I just thought it was related to recent (especially mine :) patch.

BYW, your posted v2 still doesn't have alignment on log.
Is it mailer issue ?

> And I have a question.
> This patch can’t be applied to stable branches directly by conflict.
> I found out following commits are needed to apply this patch into the 5.4 stable.
>  ASoC: soc-pcm: remove snd_soc_dpcm_be_get/set_state()
>  ASoC: soc-pcm: add snd_soc_dpcm_can_be() and remove duplicate code
> In this case, what should I do when stable maintainer requests resolving conflict to me?
> Should I send those patches to the maintainer?
> Or rewrite the patch on the latest of the each stable?

Mark, please help him

Thank you for your help !!

Best regards
---
Kuninori Morimoto


More information about the Alsa-devel mailing list