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: Mon, 02 Apr 2012 19:46:19 +1000 [thread overview]
Message-ID: <1333359979.30734.48.camel@pasglop> (raw)
In-Reply-To: <4F796C18.2040209@redhat.com>
On Mon, 2012-04-02 at 12:06 +0300, Avi Kivity wrote:
> > The current process is such that it takes absolutely forever for our
> > patches to get in, which is a major PITA for something in such state of
> > active development.
>
> If the patches were posted two weeks earlier, they would have gone in.
I believe on our side they were, but Alex took a while to make up his
tree ... oh well..
> > Why don't we have Alex tree go straight to -next like I do with Kumar
> > for example ? That way I don't need to have his branch sit in my tree
> > for weeks before I push it out to Linus.
>
> There isn't a lot of common kvm code, but what there is needs to be
> synchronized.
At least we should be able to get the important bug fixes in now, I see
that you agree in your reply to Paulus so that's good :-)
Cheers,
Ben.
next prev parent reply other threads:[~2012-04-02 9:46 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 [this message]
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=1333359979.30734.48.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