From: Avi Kivity <avi@redhat.com>
To: Paul Mackerras <paulus@samba.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
KVM list <kvm@vger.kernel.org>,
Marcelo Tosatti <mtosatti@redhat.com>,
Paul Mackerras <paulus@au1.ibm.com>,
Alexander Graf <agraf@suse.de>
Subject: Re: [GIT PULL] KVM updates for the 3.4 merge window
Date: Mon, 02 Apr 2012 12:07:04 +0300 [thread overview]
Message-ID: <4F796C38.1000908@redhat.com> (raw)
In-Reply-To: <20120401224525.GA28843@bloggs.ozlabs.ibm.com>
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
prev parent reply other threads:[~2012-04-02 9:07 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 14:08 [GIT PULL] KVM updates for the 3.4 merge window Avi Kivity
2012-03-23 0:10 ` Benjamin Herrenschmidt
2012-03-23 3:15 ` Linus Torvalds
2012-03-25 10:09 ` Avi Kivity
2012-03-25 20:51 ` Benjamin Herrenschmidt
2012-03-26 10:05 ` Avi Kivity
2012-03-26 16:21 ` Ingo Molnar
2012-03-27 7:31 ` Avi Kivity
2012-03-26 21:05 ` Benjamin Herrenschmidt
2012-03-26 21:38 ` Paul Mackerras
2012-03-27 10:09 ` Avi Kivity
2012-03-28 4:02 ` Benjamin Herrenschmidt
2012-03-28 19:41 ` Linus Torvalds
2012-03-30 12:01 ` Paul Mackerras
2012-04-01 12:38 ` Avi Kivity
2012-04-01 21:02 ` Benjamin Herrenschmidt
2012-04-02 9:06 ` Avi Kivity
2012-04-02 9:46 ` Benjamin Herrenschmidt
2012-04-16 12:47 ` Alexander Graf
2012-04-16 12:53 ` Avi Kivity
2012-04-16 13:05 ` Alexander Graf
2012-04-16 23:05 ` Benjamin Herrenschmidt
2012-04-17 7:20 ` Avi Kivity
2012-04-17 9:34 ` Alexander Graf
2012-04-17 10:25 ` Avi Kivity
2012-04-01 22:45 ` Paul Mackerras
2012-04-02 9:07 ` Avi Kivity [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=4F796C38.1000908@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=benh@kernel.crashing.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=paulus@au1.ibm.com \
--cc=paulus@samba.org \
/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