From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [GIT PULL] KVM updates for the 3.4 merge window Date: Mon, 02 Apr 2012 12:06:32 +0300 Message-ID: <4F796C18.2040209@redhat.com> References: <4F688F48.6090303@redhat.com> <1332461414.2982.90.camel@pasglop> <4F6EEEC1.4030608@redhat.com> <20120326213809.GA29788@bloggs.ozlabs.ibm.com> <4F7191E8.7020804@redhat.com> <20120330120107.GA28503@bloggs.ozlabs.ibm.com> <4F784C4D.3000409@redhat.com> <1333314138.30734.17.camel@pasglop> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Paul Mackerras , Linus Torvalds , linux-kernel , KVM list , Marcelo Tosatti , Paul Mackerras , Alexander Graf To: Benjamin Herrenschmidt Return-path: Received: from mx1.redhat.com ([209.132.183.28]:4790 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751354Ab2DBJGo (ORCPT ); Mon, 2 Apr 2012 05:06:44 -0400 In-Reply-To: <1333314138.30734.17.camel@pasglop> Sender: kvm-owner@vger.kernel.org List-ID: On 04/02/2012 12:02 AM, Benjamin Herrenschmidt wrote: > On Sun, 2012-04-01 at 15:38 +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. > > These are all powerpc specific patches that have been cooking in Alex > tree for a while and elsewhere before that. They almost only affect > arch/powerpc/kvm, and as such don't really need a lot of integration > testing in -next. A bit for sure but not necessarily monthes. > > 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. > 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. -- error compiling committee.c: too many arguments to function