* [PATCH v3 0/1] ASoC: dpcm: acquire dpcm_lock in dpcm_do_trigger() [not found] <CGME20201214083825epcas2p3c1b9e236ec1342195c46d91c6f29fb21@epcas2p3.samsung.com> @ 2020-12-14 8:38 ` Gyeongtaek Lee 0 siblings, 0 replies; 3+ messages in thread From: Gyeongtaek Lee @ 2020-12-14 8:38 UTC (permalink / raw) To: 'Kuninori Morimoto', cpgs Cc: alsa-devel, khw0178.kim, 'Takashi Iwai', lgirdwood, 'Pierre-Louis Bossart', kimty, donggyun.ko, hmseo, cpgs, s47.kang, pilsun.jang, tkjung >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 -- 2.21.0 ^ permalink raw reply [flat|nested] 3+ messages in thread
[parent not found: <CGME20201228112315epcas2p46266c89ffb53b307a1d751a590d06ad0@epcas2p4.samsung.com>]
* [PATCH v3 0/1] ASoC: dpcm: acquire dpcm_lock in dpcm_do_trigger() [not found] <CGME20201228112315epcas2p46266c89ffb53b307a1d751a590d06ad0@epcas2p4.samsung.com> @ 2020-12-28 11:23 ` Gyeongtaek Lee 0 siblings, 0 replies; 3+ messages in thread From: Gyeongtaek Lee @ 2020-12-28 11:23 UTC (permalink / raw) To: 'Kuninori Morimoto', broonie, cpgs Cc: alsa-devel, khw0178.kim, 'Takashi Iwai', lgirdwood, 'Pierre-Louis Bossart', kimty, donggyun.ko, hmseo, cpgs, s47.kang, pilsun.jang, tkjung >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 -- 2.21.0 ^ permalink raw reply [flat|nested] 3+ messages in thread
[parent not found: <CGME20201203085858epcas2p1258c4c14b9398a15fb348ab92e306a25@epcas2p1.samsung.com>]
* [PATCH v3 0/1] ASoC: dpcm: acquire dpcm_lock in dpcm_do_trigger() [not found] <CGME20201203085858epcas2p1258c4c14b9398a15fb348ab92e306a25@epcas2p1.samsung.com> @ 2020-12-03 8:58 ` Gyeongtaek Lee 0 siblings, 0 replies; 3+ messages in thread From: Gyeongtaek Lee @ 2020-12-03 8:58 UTC (permalink / raw) To: 'Kuninori Morimoto', cpgs Cc: alsa-devel, khw0178.kim, 'Takashi Iwai', lgirdwood, 'Pierre-Louis Bossart', kimty, donggyun.ko, hmseo, cpgs, s47.kang, pilsun.jang, tkjung >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 -- 2.21.0 ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2020-12-28 12:21 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <CGME20201214083825epcas2p3c1b9e236ec1342195c46d91c6f29fb21@epcas2p3.samsung.com>
2020-12-14 8:38 ` [PATCH v3 0/1] ASoC: dpcm: acquire dpcm_lock in dpcm_do_trigger() Gyeongtaek Lee
[not found] <CGME20201228112315epcas2p46266c89ffb53b307a1d751a590d06ad0@epcas2p4.samsung.com>
2020-12-28 11:23 ` Gyeongtaek Lee
[not found] <CGME20201203085858epcas2p1258c4c14b9398a15fb348ab92e306a25@epcas2p1.samsung.com>
2020-12-03 8:58 ` Gyeongtaek Lee
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox