From: Mark Brown <broonie@kernel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: alsa-devel@alsa-project.org, Brown@sirena.org.uk,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
tiwai@suse.de, Takashi Iwai <tiwai@suse.com>,
open list <linux-kernel@vger.kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
liam.r.girdwood@linux.intel.com, vkoul@kernel.org,
Mark@sirena.org.uk
Subject: Re: [RFC PATCH 1/2] ASoC: soc-pcm: protect BE dailink state changes in trigger
Date: Mon, 30 Aug 2021 12:15:35 +0100 [thread overview]
Message-ID: <YSy91xTP/5oSedrZ@sirena.org.uk> (raw)
In-Reply-To: <27b9fe7a-18cc-61ee-1e4d-72282d8eaa82@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 341 bytes --]
On Thu, Aug 26, 2021 at 02:24:19PM -0500, Pierre-Louis Bossart wrote:
> Ah sorry, there were still some issues in this RFC, we did more testing
> and came up with a lot of improvements. The intent of the RFC status was
> also to make sure it wasn't applied before the merge window.
> Can this be reverted in your branch Mark?
Ugh, right.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-08-30 11:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 16:40 [RFC PATCH 0/2] ASoC: soc-pcm: fix trigger race conditions with shared BE Pierre-Louis Bossart
2021-08-17 16:40 ` [RFC PATCH 1/2] ASoC: soc-pcm: protect BE dailink state changes in trigger Pierre-Louis Bossart
2021-08-26 18:30 ` Mark Brown
2021-08-26 19:24 ` Pierre-Louis Bossart
2021-08-30 11:15 ` Mark Brown [this message]
2021-08-17 16:40 ` [RFC PATCH 2/2] ASoC: soc-pcm: test refcount before triggering 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=YSy91xTP/5oSedrZ@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Brown@sirena.org.uk \
--cc=Mark@sirena.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.com \
--cc=tiwai@suse.de \
--cc=vkoul@kernel.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