From: Vinod Koul <vinod.koul@intel.com>
To: Richard Fitzgerald <rf@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org,
pierre-louis.bossart@linux.jf.intel.com,
ckeepax@opensource.wolfsonmicro.com
Subject: Re: [tinycompress][PATCH 0/2] Fixes for write loop logic
Date: Fri, 7 Jun 2013 06:00:25 +0530 [thread overview]
Message-ID: <20130607003025.GE23045@intel.com> (raw)
In-Reply-To: <20130605120827.GA21556@opensource.wolfsonmicro.com>
On Wed, Jun 05, 2013 at 01:08:27PM +0100, Richard Fitzgerald wrote:
> Two small patches which correct the logic of compress_write()
> so that it will work correctly if asked to write a buffer
> shorter than the fragment length. The first patch is needed
> to ensure that if the client requests auto-configuration
> of fragment size the internal copy of the config contains the
> configured fragment size. The second patch contains the actual
> fix to the write loop logic.
>
> Richard Fitzgerald (2):
> compress: copy final version of config struct
> compress: do not poll if enough space to write remaining data
Applied thanks
--
~Vinod
>
> compress.c | 13 ++++++-------
> 1 files changed, 6 insertions(+), 7 deletions(-)
>
> --
> 1.7.2.5
>
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
--
prev parent reply other threads:[~2013-06-07 1:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 12:08 [tinycompress][PATCH 0/2] Fixes for write loop logic Richard Fitzgerald
2013-06-05 12:10 ` [tinycompress][PATCH 1/2] compress: copy final version of config struct Richard Fitzgerald
2013-06-05 12:11 ` [tinycompress][PATCH 2/2] compress: do not poll if enough space to write remaining data Richard Fitzgerald
2013-06-07 0:30 ` 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=20130607003025.GE23045@intel.com \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=pierre-louis.bossart@linux.jf.intel.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