[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20130208084029.d7d97d6e26580a5512712f91@canb.auug.org.au>
Date: Fri, 8 Feb 2013 08:40:29 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Ingo Molnar <mingo@...nel.org>
Cc: David Rientjes <rientjes@...gle.com>,
Pekka Enberg <penberg@...nel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Sasha Levin <levinsasha928@...il.com>,
Randy Dunlap <rdunlap@...radead.org>,
David Woodhouse <dwmw2@...radead.org>,
Michal Marek <mmarek@...e.cz>,
"H. Peter Anvin" <hpa@...or.com>, tglx@...utronix.de,
"H. Peter Anvin" <hpa@...ux.intel.com>,
linux-kernel@...r.kernel.org
Subject: Re: kvmtool tree (Was: Re: [patch] config: fix make kvmconfig)
Hi Ingo,
On Wed, 6 Feb 2013 22:46:46 +0100 Ingo Molnar <mingo@...nel.org> wrote:
>
> Pekka still intends to send it in the next merge window AFAIK,
That has been true since v3.2 :-(
> and I use it for testing rather frequently so I'm not going to
> remove it from my tree for the time being.
I didn't ask you to remove it from your tree, I just would like it
removed from that branch that is included in linux-next
(tip/auto-latest). I know others who also use it for testing.
> Note that I never actually had any maintenance problems due to
> it: it's orthogonal, and as long as you don't use it explicitly
> (such as its 'make kvmconfig' feature - which is rather handy)
> it never actually broke anything.
I don't doubt any of that, it is just that Linus has explicitly said that
he will not pull it into his tree. Thus, it should not be in linux-next.
--
Cheers,
Stephen Rothwell sfr@...b.auug.org.au
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists