All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Richard Fitzgerald <rf@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH TINYCOMPRESS 14/14] cplay: support auto-configuration of fragment size and count
Date: Mon, 11 Feb 2013 00:53:12 -0800	[thread overview]
Message-ID: <20130211085311.GC3789@intel.com> (raw)
In-Reply-To: <20130210002340.GN31139@opensource.wolfsonmicro.com>

On Sun, Feb 10, 2013 at 12:23:40AM +0000, Richard Fitzgerald wrote:

I tried applying rest, but looks like patches you have generated against is
older one. Can you rebase all your patches on the tip and resend for those I
didnt comment first.

Also would nice to use cover letter while sending a series, --cover-letter
option is your friend

--
~Vinod

  reply	other threads:[~2013-02-11  9:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-10  0:23 [PATCH TINYCOMPRESS 14/14] cplay: support auto-configuration of fragment size and count Richard Fitzgerald
2013-02-11  8:53 ` Vinod Koul [this message]
2013-02-11  9:58   ` Richard Fitzgerald
2013-02-11 10:43     ` Vinod Koul
2013-02-11 10:10   ` Richard Fitzgerald
2013-02-22 16:11 ` [PATCH TINYCOMPRESS 14/14 v2] " Richard Fitzgerald

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=20130211085311.GC3789@intel.com \
    --to=vinod.koul@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.