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: Tue, 27 Mar 2012 08:38:09 +1100 [thread overview]
Message-ID: <20120326213809.GA29788@bloggs.ozlabs.ibm.com> (raw)
In-Reply-To: <4F6EEEC1.4030608@redhat.com>
On Sun, Mar 25, 2012 at 12:09:05PM +0200, Avi Kivity wrote:
> I can switch to fast-forward-only in the future, but I'm afraid that
> this particular tree is broken for good. The un-rebased
> fast-forward-only source for this is kvm.git master, which I don't think
> you want to pull. It will cause every kvm commit to appear twice and
> confuse everyone.
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?
Paul.
next prev parent reply other threads:[~2012-03-26 21:38 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 [this message]
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
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=20120326213809.GA29788@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®