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 ?

Sorry. I didn't fully understand what alignment means. I fixed the log by looking at some previous commits.

Thank you so much.

Gyeongtaek Lee

...

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

Gyeongtaek Lee (1): ASoC: dpcm: acquire dpcm_lock in dpcm_do_trigger()

sound/soc/soc-pcm.c | 62 ++++++++++++++++++++++++++++++++------------- 1 file changed, 44 insertions(+), 18 deletions(-)

base-commit: fa02fcd94b0c8dff6cc65714510cf25ad194b90d