public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Avi Kivity <avi@redhat.com>
Cc: Paul Mackerras <paulus@samba.org>,
	Linus Torvalds <torvalds@linux-foundation.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: Wed, 28 Mar 2012 15:02:39 +1100	[thread overview]
Message-ID: <1332907359.2882.77.camel@pasglop> (raw)
In-Reply-To: <4F7191E8.7020804@redhat.com>

On Tue, 2012-03-27 at 12:09 +0200, Avi Kivity wrote:

> 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 remove Alex's commits, Alex sends me a pull request based on that
> tree, I pull it in.  Alex being away for three weeks is a minor flaw in
> this plan.
> - As above, but with you sending me that tree as temporary kvm-ppc
> maintainer.
> 
> Options 2/3 are harder as there are a few interdependencies.
> 
> Linus, if the first option is acceptable, a tree is available at the
> same place:
> 
>   git://git.kernel.org/pub/scm/virt/kvm/kvm.git kvm-updates/3.4
> 
> otherwise, please provide guidance.

Linus, what's your feeling here ? I'd really like to have the bulk of
the powerpc updates this time around, they already missed the previous
merge window due to maintainers taking too long to deal with their
inbox :-) 

KVM ppc is a big WIP with little if any users at this point so the risk
of breaking things is near to non-existent, it all boils down to making
our own life easier by having stuff not drifting out of tree (and making
it possible for distros to pick it up when they decide to do so).

Cheers,
Ben.



  reply	other threads:[~2012-03-28  4:03 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 [this message]
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=1332907359.2882.77.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=agraf@suse.de \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=paulus@au1.ibm.com \
    --cc=paulus@samba.org \
    --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