From: Vinod Koul <vinod.koul@intel.com>
To: Richard Fitzgerald <rf@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH] crec: Always read whole number of fragments when length limit specified
Date: Mon, 7 Dec 2015 10:26:21 +0530 [thread overview]
Message-ID: <20151207045621.GJ1854@localhost> (raw)
In-Reply-To: <1449141935-23350-1-git-send-email-rf@opensource.wolfsonmicro.com>
On Thu, Dec 03, 2015 at 11:25:35AM +0000, Richard Fitzgerald wrote:
> This patch removes the lines that adjusted the read size to exactly
> read to the end of the calculated length in bytes. Doing this could
> lead to invalid fragment sizes being requested which may then cause
> a read error on some codecs.
>
> Instead we keep reading whole fragments until we have >= length bytes
> of data captured.
Applied, thanks
--
~Vinod
prev parent reply other threads:[~2015-12-07 4:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 11:25 [PATCH] crec: Always read whole number of fragments when length limit specified Richard Fitzgerald
2015-12-07 4:56 ` Vinod Koul [this message]
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=20151207045621.GJ1854@localhost \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=patches@opensource.wolfsonmicro.com \
--cc=rf@opensource.wolfsonmicro.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;
as well as URLs for NNTP newsgroup(s).