[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20121114162448.e2b05b1be8c62bcb64cc7d42@canb.auug.org.au>
Date: Wed, 14 Nov 2012 16:24:48 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Pekka Enberg <penberg@...nel.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Ingo Molnar <mingo@...nel.org>, Avi Kivity <avi@...hat.com>,
linux-kernel@...r.kernel.org, Christoph Hellwig <hch@...radead.org>
Subject: Re: [GIT PULL] Linux KVM tool for v3.7-rc0
Hi all again,
On Sat, 20 Oct 2012 18:04:36 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> On Tue, 16 Oct 2012 07:50:52 -0700 Linus Torvalds <torvalds@...ux-foundation.org> wrote:
> >
> > On Mon, Oct 15, 2012 at 7:41 PM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> > >>
> > >> git://git.kernel.org/pub/scm/linux/kernel/git/penberg/linux.git kvmtool/for-linus
> > >
> > > So you have not taken this in the v3.7 merge window.
> > >
> > > Will you ever merge this?
> >
> > I have yet to see a compelling argument for merging it. It's tons of
> > code, it doesnt match the original "small simple" model, and I think
> > it would be better off as a separate project.
>
> So are there any compelling arguments from the proponents, or can I
> remove this from linux-next (and have it removed from the tip auto-latest
> branch)?
So, where did we get to? I *think* the consensus was that the KVM tool
did not need to be in the kernel tree, right? In which case:
1) I need to remove the kvmtool tree from linux-next
2) the same code needs to be removed from the tip tree
hmm?
--
Cheers,
Stephen Rothwell sfr@...b.auug.org.au
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists