From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pekka Enberg Subject: Re: linux-next: fate of the kvmtool tree Date: Wed, 3 Oct 2012 09:47:34 +0300 Message-ID: References: <20121003152921.c08e7019d2ada843888a2570@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: Received: from mail-we0-f174.google.com ([74.125.82.174]:34297 "EHLO mail-we0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753033Ab2JCGrg (ORCPT ); Wed, 3 Oct 2012 02:47:36 -0400 In-Reply-To: <20121003152921.c08e7019d2ada843888a2570@canb.auug.org.au> Sender: linux-next-owner@vger.kernel.org List-ID: To: Stephen Rothwell Cc: Sasha Levin , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Peter Zijlstra , linux-next@vger.kernel.org, LKML , Linus , Andrew Morton Hi Stephen, On Wed, Oct 3, 2012 at 8:29 AM, Stephen Rothwell wrote: > Well, here we are at another merge window and the kvmtool tree is still > not merged. So, is it likely that it will be merged in this merge > window? or the next? If not, can I please remove it from linux-next > (and have it removed from the auto-latest branch of the tip tree) as it > just adds weight to the patches and the tree that people have to fetch to > work with. I have no idea how likely it is that it will be merged but I'm planning to send a pull request for this merge cycle. ;-) Btw, IIRC the KVM tool also ends up in linux-next via Ingo's tree so dropping my tree might not be enough. Pekka