From: Ricardo Biehl Pasquali <pasqualirb@gmail.com>
To: Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org
Subject: Re: Patch "ALSA: pcm: Return 0 when size < start_threshold in capture" has been added to the 4.19-stable tree
Date: Wed, 11 Sep 2019 11:14:31 -0300 [thread overview]
Message-ID: <20190911141431.GA21115@localhost.localdomain> (raw)
In-Reply-To: <20190911093035.57F102089F@mail.kernel.org>
On Wed, Sep 11, 2019 at 05:30:33AM -0400, Sasha Levin wrote:
> This is a note to let you know that I've just added the patch titled
>
> ALSA: pcm: Return 0 when size < start_threshold in capture
>
> to the 4.19-stable tree which can be found at:
> http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>
> The filename of the patch is:
> alsa-pcm-return-0-when-size-start_threshold-in-captu.patch
> and it can be found in the queue-4.19 subdirectory.
>
> If you, or anyone else, feels it should not be added to the stable tree,
> please let <stable@vger.kernel.org> know about it.
Hi Sasha.
This patch was reverted by the commit 932a81519572156a88db
("ALSA: pcm: Comment why read blocks when PCM is not
running"):
This avoids bringing back the problem introduced by
62ba568f7aef ("ALSA: pcm: Return 0 when size <
start_threshold in capture") and fixed in 00a399cad1a0
("ALSA: pcm: Revert capture stream behavior change in
blocking mode"), which prevented the user from starting
capture from another thread.
Should this be queued anyway? If yes, I think it should also
be queued the fix and the commit above.
pasquali
next parent reply other threads:[~2019-09-11 14:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190911093035.57F102089F@mail.kernel.org>
2019-09-11 14:14 ` Ricardo Biehl Pasquali [this message]
2019-09-11 14:20 ` Patch "ALSA: pcm: Return 0 when size < start_threshold in capture" has been added to the 4.19-stable tree Ricardo Biehl Pasquali
2019-09-11 16:49 ` Sasha Levin
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=20190911141431.GA21115@localhost.localdomain \
--to=pasqualirb@gmail.com \
--cc=sashal@kernel.org \
--cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).