From: Vinod Koul <vinod.koul@intel.com>
To: Charles Keepax <ckeepax@opensource.cirrus.com>
Cc: patches@opensource.cirrus.com, alsa-devel@alsa-project.org
Subject: Re: [PATCH][tinycompress] crecord: Use whole buffer requested by user
Date: Thu, 19 Apr 2018 11:36:00 +0530 [thread overview]
Message-ID: <20180419060557.GG6014@localhost> (raw)
In-Reply-To: <20180413115859.20310-1-ckeepax@opensource.cirrus.com>
On Fri, Apr 13, 2018 at 12:58:59PM +0100, Charles Keepax wrote:
> Currently, crecord will only actually use 1 fragment worth of its
> internal buffer no matter what the user requests. Correct this so that
> the whole buffer requested by the user is used for copying data.
Applied, thanks
--
~Vinod
prev parent reply other threads:[~2018-04-19 6:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 11:58 [PATCH][tinycompress] crecord: Use whole buffer requested by user Charles Keepax
2018-04-19 6:06 ` 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=20180419060557.GG6014@localhost \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=patches@opensource.cirrus.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