From: "Amadeusz Sławiński" <amadeuszx.slawinski@linux.intel.com>
To: Vinod Koul <vkoul@kernel.org>
Cc: alsa-devel@alsa-project.org,
Charles Keepax <ckeepax@opensource.cirrus.com>,
linux-kernel@vger.kernel.org,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Takashi Iwai <tiwai@suse.com>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Subject: Re: [PATCH v4 1/3] ALSA: compress: document the compress audio state machine
Date: Mon, 29 Jun 2020 12:02:30 +0200 [thread overview]
Message-ID: <3a43467a-5432-a3ef-2250-2ac1054539d0@linux.intel.com> (raw)
In-Reply-To: <20200629093429.GA2599@vkoul-mobl>
On 6/29/2020 11:34 AM, Vinod Koul wrote:
>
> Not sure, this is not in the version I posted, arrow is from setup ->
> prepare. See
https://lore.kernel.org/alsa-devel/20200629075002.11436-2-vkoul@kernel.org/
>
> I don't know how it got reversed in your version, maybe the MUA messed
> up??
>
Ah... I must have edited it myself when preparing edited version, sorry
for noise ;)
> a compr_write() moves from SETUP -> PREPARE. Fixing that above looks
> better version of mine..
Yes, I feel it is easier to understand, A redirect confused me for a
short bit when I first looked at graph and it can be easily avoided.
next prev parent reply other threads:[~2020-06-29 19:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 7:49 [PATCH v4 0/3] ALSA: compress: Document stream states and fix gapless SM Vinod Koul
2020-06-29 7:50 ` [PATCH v4 1/3] ALSA: compress: document the compress audio state machine Vinod Koul
2020-06-29 9:05 ` Amadeusz Sławiński
2020-06-29 9:34 ` Vinod Koul
2020-06-29 10:02 ` Amadeusz Sławiński [this message]
2020-06-29 10:59 ` Vinod Koul
2020-06-29 7:50 ` [PATCH v4 2/3] ALSA: compress: document the compress gapless " Vinod Koul
2020-06-29 7:50 ` [PATCH v4 3/3] ALSA: compress: fix partial_drain completion state Vinod Koul
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=3a43467a-5432-a3ef-2250-2ac1054539d0@linux.intel.com \
--to=amadeuszx.slawinski@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=tiwai@suse.com \
--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
Powered by JetHome