[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOJsxLEadL8USuW5zEuaW-OexEbgZvqdj5U6u5gEgOyQ5LCLRA@mail.gmail.com>
Date: Wed, 6 Feb 2013 22:45:53 +0200
From: Pekka Enberg <penberg@...nel.org>
To: David Rientjes <rientjes@...gle.com>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Ingo Molnar <mingo@...nel.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: [patch] config: fix make kvmconfig
On Wed, Feb 6, 2013 at 10:12 PM, David Rientjes <rientjes@...gle.com> wrote:
> What's the endgame for kvmtool/next? The patch that this fixes has been
> sitting in linux-next for over 15 months and hasn't been pulled by Linus,
> yet some find it to be quite useful.
>
> Is it a permanent addition to linux-next, is there a route to mainline,
> or something else?
It is actively developed and has recently gained support for ARM, for
example. Ingo keeps pulling it to the -tip tree so tools/kvm also
appears on linux-next through that. Linus doesn't think it's worth
pulling and the KVM maintainers are uninterested.
So I guess we've deadlocked the Linux kernel development process?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists