All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: �̰��� <gt82.lee@samsung.com>
Cc: alsa-devel@alsa-project.org, lgirdwood@gmail.com, tiwai@suse.com
Subject: Re: [PATCH 1/1] ASoC: soc-compress: lock pcm_mutex to resolve lockdep error
Date: Mon, 30 Mar 2020 11:33:07 +0100	[thread overview]
Message-ID: <20200330103307.GB4792@sirena.org.uk> (raw)
In-Reply-To: <000f01d60631$a96b8b50$fc42a1f0$@samsung.com>

[-- Attachment #1: Type: text/plain, Size: 517 bytes --]

On Mon, Mar 30, 2020 at 10:22:21AM +0900, �̰��� wrote:

> >snd_soc_runtime_activate() and snd_soc_runtime_deactivate()
> >require pcm_mutex lock.
> >
> >Signed-off-by: Gyeongtaek Lee <gt82.lee@samsung.com>
> >---
> > sound/soc/soc-compress.c | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> >diff --git a/sound/soc/soc-compress.c b/sound/soc/soc-compress.c

I can't do anything with this patch as it's quoted, please resend.
Please also remember to CC Vinod, the compressed audio maintainer.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-03-30 10:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20200326084608epcas2p32239121f201613573e7dd86c3172a29f@epcas2p3.samsung.com>
2020-03-26  8:46 ` [PATCH 1/1] ASoC: soc-compress: lock pcm_mutex to resolve lockdep error 이경택
2020-03-30  1:22   ` 이경택
2020-03-30 10:33     ` Mark Brown [this message]
     [not found] <CGME20200330110126epcas2p4525e5c6f61f7452df008696f9153770d@epcas2p4.samsung.com>
2020-03-30 11:01 ` 이경택
2020-03-30 11:47   ` Vinod Koul
2020-03-31  1:54     ` 이경택
2020-04-02  2:44       ` Gyeongtaek Lee
2020-04-03  7:55       ` Vinod Koul
2020-04-09  1:32         ` Gyeongtaek Lee

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200330103307.GB4792@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=gt82.lee@samsung.com \
    --cc=lgirdwood@gmail.com \
    --cc=tiwai@suse.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.