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 02:43:57 -0800 [thread overview]
Message-ID: <20130211104357.GF3789@intel.com> (raw)
In-Reply-To: <20130211095845.GA27658@opensource.wolfsonmicro.com>
On Mon, Feb 11, 2013 at 09:58:45AM +0000, Richard Fitzgerald wrote:
> > looks like patches you have generated against is
> > older one.
>
> Yes this is true, which is how it should be.
> These patches and the ones from Charles Keepax
> are a single development line, and Charles's patches
> were based on top of this sequence.
> What's happened is that the patches from Charles
> have been upstreamed and applied out-of-order.
> These 14 should be applied, and then the set from
> Charles.
That is not how it works. Since Charles sent his patches first I applied those.
Now these will _need_ to based on tip of the tree you are targetting not on some
older rev.
If you have internal dependecies you should have internally sorted that out!
Now pls rebase these
--
~Vinod
next prev parent reply other threads:[~2013-02-11 11:08 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
2013-02-11 9:58 ` Richard Fitzgerald
2013-02-11 10:43 ` Vinod Koul [this message]
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=20130211104357.GF3789@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 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).