From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexander Graf Subject: Re: [GIT PULL] KVM updates for the 3.4 merge window Date: Tue, 17 Apr 2012 11:34:21 +0200 Message-ID: <4F8D391D.8080008@suse.de> 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> <4F796C18.2040209@redhat.com> <1333359979.30734.48.camel@pasglop> <3BB9812B-6FE2-4370-9D55-D273364BFFD1@suse.de> <4F8C1652.7000004@redhat.com> <1334617517.25353.17.camel@pasglop> <4F8D19D3.1060002@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Benjamin Herrenschmidt , Paul Mackerras , Linus Torvalds , linux-kernel , KVM list , Marcelo Tosatti , Paul Mackerras To: Avi Kivity Return-path: In-Reply-To: <4F8D19D3.1060002@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 04/17/2012 09:20 AM, Avi Kivity wrote: > On 04/17/2012 02:05 AM, Benjamin Herrenschmidt wrote: >> On Mon, 2012-04-16 at 15:53 +0300, Avi Kivity wrote: >>> kvm.git next is exposed to linux-next, where they get tested quite a >>> lot. Granted it's mostly build testing, and people are unlikely to >>> test >>> kvm there, but they will test the non-kvm bits that creep in there. >>> >>>> The alternative would be that I don't have a -next tree, just >>> collect patches and immediately send them to Avi. That way the main >>> kvm tree would be broken more often, but at least we don't get these >>> horrible synchronization latencies. >>> >>> That works too. Don't post immediately; 2-3 week batches would reduce >>> noise. >> Or do like I do with Kumar for FSL stuff... his stuff gets pulled via my >> tree but his tree is in linux-next as well. There's no reason not to do >> that. >> >> That way, his next branch gets linux-next coverage whether it's in my >> tree or not, and I pull when I put the final powerpc-next together, >> which gives me a chance to do a quick vet "just in case" and sort out >> any major conflict before it all goes to Linus. >> > Sure, that works too. Sounds even easier to me. So how do I get my tree into linux-next? Alex