From: Paul Mackerras <paulus@samba.org>
To: Avi Kivity <avi@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
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: Fri, 30 Mar 2012 23:01:07 +1100 [thread overview]
Message-ID: <20120330120107.GA28503@bloggs.ozlabs.ibm.com> (raw)
In-Reply-To: <4F7191E8.7020804@redhat.com>
On Tue, Mar 27, 2012 at 12:09:44PM +0200, Avi Kivity wrote:
> > There are patches from me in there that have been pending since
> > December last year, and now look like they won't be going upstream
> > until June. So, under the circumstances, how would you (Avi) feel
> > about Ben and I committing the KVM patches that only affect powerpc to
> > Ben's tree and sending them to Linus that way before the merge window
> > closes?
>
> That's fine if there are no interdependencies. It looks like 74df956
> will be a problem though.
>
> The other two options are:
>
> - I'll add my signoff to the commits that lack it. This unbreaks the
> committer lacks signoff.
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?
Thanks,
Paul.
next prev parent reply other threads:[~2012-03-30 12:03 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 14:08 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 [this message]
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
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=20120330120107.GA28503@bloggs.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=agraf@suse.de \
--cc=avi@redhat.com \
--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=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®