From: Mark Brown <broonie@kernel.org>
To: Guillaume Tucker <guillaume.tucker@collabora.com>
Cc: Takashi Iwai <tiwai@suse.de>,
Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
tomeu.vizoso@collabora.com, mgalka@collabora.com,
matthew.hart@linaro.org, khilman@baylibre.com,
enric.balletbo@collabora.com, Liam Girdwood <lgirdwood@gmail.com>,
alsa-devel@alsa-project.org,
"kernelci.org bot" <bot@kernelci.org>,
linux-kernel@vger.kernel.org,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: Re: [alsa-devel] next/master boot bisection: next-20190528 on sun8i-h3-libretech-all-h3-cc
Date: Fri, 7 Jun 2019 20:00:21 +0100 [thread overview]
Message-ID: <20190607190021.GK2456@sirena.org.uk> (raw)
In-Reply-To: <8ca25787-fc03-7942-0705-3ec7d88862a6@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 910 bytes --]
On Fri, Jun 07, 2019 at 05:31:12PM +0100, Guillaume Tucker wrote:
> On 30/05/2019 16:53, Takashi Iwai wrote:
> >> + mutex_lock(&client_mutex);
> >> for_each_rtdcom(rtd, rtdcom) {
> >> component = rtdcom->component;
> >>
> >> if (component->driver->remove_order == order)
> >> soc_remove_component(component);
> >> }
> >> + mutex_unlock(&client_mutex);
> > Ranjani, which code path your patch tries to address? Maybe better to
> > wrap client_mutex() in the caller side like snd_soc_unbind_card()?
> Is anyone looking into this issue?
> It is still occurring in next-20190606, there was a bisection
> today which landed on the same commit. There just hasn't been
> any new bisection reports because they have been temporarily
> disabled while we fix some issues on kernelci.org.
I was expecting that Ranjani or one of the other Intel people was
looking into it...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-06-07 19:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 9:16 next/master boot bisection: next-20190528 on sun8i-h3-libretech-all-h3-cc kernelci.org bot
2019-05-30 15:53 ` [alsa-devel] " Takashi Iwai
2019-06-07 16:31 ` Guillaume Tucker
2019-06-07 19:00 ` Mark Brown [this message]
2019-06-07 20:08 ` Pierre-Louis Bossart
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=20190607190021.GK2456@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bot@kernelci.org \
--cc=enric.balletbo@collabora.com \
--cc=guillaume.tucker@collabora.com \
--cc=khilman@baylibre.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.hart@linaro.org \
--cc=mgalka@collabora.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=tiwai@suse.de \
--cc=tomeu.vizoso@collabora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox