From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
To: Rohit Kumar <rohitkr@codeaurora.org>
Cc: Mark Brown <broonie@kernel.org>,
Ajit Pandey <ajitp@codeaurora.org>,
rohkumar@qti.qualcomm.com, alsa-devel@alsa-project.org,
bgoswami@codeaurora.org, vinod.koul@linaro.org,
linux-kernel@vger.kernel.org, plai@codeaurora.org,
tiwai@suse.com, lgirdwood@gmail.com, asishb@codeaurora.org,
srinivas.kandagatla@linaro.org
Subject: Re: [alsa-devel] Applied "ASoC: soc-core: defer card probe until all component is added to list" to the asoc tree
Date: 10 Jan 2019 16:29:25 +0900 [thread overview]
Message-ID: <87y37t9e08.wl-kuninori.morimoto.gx@renesas.com> (raw)
In-Reply-To: <961ef85b-86a5-1db8-260b-6c5cb27399fe@codeaurora.org>
Hi Rohit
> > I got below WARNING by this patch.
> > I guess we need mutex_lock() on snd_soc_register_card() ?
>
> Right, we should have client_mutex lock before calling
> soc_find_component().
>
> We will post fix.
Thanks !!
Best regards
---
Kuninori Morimoto
next prev parent reply other threads:[~2019-01-10 7:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 8:47 [PATCH v2] ASoC: soc-core: defer card probe until all component is added to list Rohit kumar
2019-01-09 12:49 ` Applied "ASoC: soc-core: defer card probe until all component is added to list" to the asoc tree Mark Brown
2019-01-10 2:32 ` [alsa-devel] " Kuninori Morimoto
2019-01-10 7:09 ` Rohit Kumar
2019-01-10 7:29 ` Kuninori Morimoto [this message]
2019-01-11 5:07 ` [alsa-devel] [PATCH v2] ASoC: soc-core: defer card probe until all component is added to list Pierre-Louis Bossart
2019-01-11 8:11 ` Rohit Kumar
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=87y37t9e08.wl-kuninori.morimoto.gx@renesas.com \
--to=kuninori.morimoto.gx@renesas.com \
--cc=ajitp@codeaurora.org \
--cc=alsa-devel@alsa-project.org \
--cc=asishb@codeaurora.org \
--cc=bgoswami@codeaurora.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=plai@codeaurora.org \
--cc=rohitkr@codeaurora.org \
--cc=rohkumar@qti.qualcomm.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=tiwai@suse.com \
--cc=vinod.koul@linaro.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).