[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4F796C38.1000908@redhat.com>
Date: Mon, 02 Apr 2012 12:07:04 +0300
From: Avi Kivity <avi@...hat.com>
To: Paul Mackerras <paulus@...ba.org>
CC: Benjamin Herrenschmidt <benh@...nel.crashing.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
KVM list <kvm@...r.kernel.org>,
Marcelo Tosatti <mtosatti@...hat.com>,
Paul Mackerras <paulus@....ibm.com>,
Alexander Graf <agraf@...e.de>
Subject: Re: [GIT PULL] KVM updates for the 3.4 merge window
On 04/02/2012 01:45 AM, Paul Mackerras wrote:
> On Sun, Apr 01, 2012 at 03:38:37PM +0300, Avi Kivity wrote:
> > On 03/30/2012 03:01 PM, Paul Mackerras wrote:
> > > I just noticed that the branch you asked Linus to pull includes none
> > > of the patches that Alex sent you in the last batch, in the email with
> > > subject "[PULL 00/56] ppc patch queue 2012-03-15" sent on March 15,
> > > where he asked you to pull git://github.com/agraf/linux-2.6.git
> > > for-upstream.
> > >
> > > What happened? Did they get lost in the re-signing, or is there some
> > > reason you thought they shouldn't go in?
> >
> > That pull request was send three days before the merge window opened;
> > patches are supposed to cook for a while in -next before being merged,
> > especially large trees like that one.
>
> OK. Then there are about six commits from that string that are small,
> simple fixes for bugs introduced in earlier patches, that only affect
> arch/powerpc. They should go into Linus' tree as soon as possible.
Sure.
> How do you want to handle those? Do you want them as patches or as a
> git tree, and if the latter, what do you prefer that I base them on?
> Or should I send them in via Ben?
Git tree against upstream please.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists