From: Pekka Enberg <penberg@kernel.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Avi Kivity <avi@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Linux KVM tool for v3.7-rc0
Date: Thu, 18 Oct 2012 13:31:40 +0300 (EEST) [thread overview]
Message-ID: <alpine.LFD.2.02.1210181325460.9682@tux.localdomain> (raw)
In-Reply-To: <20121018100312.GB14814@gmail.com>
On Thu, 18 Oct 2012, Ingo Molnar wrote:
> * Christoph Hellwig <hch@infradead.org> wrote:
>
> > On Fri, Oct 12, 2012 at 02:34:33PM +0300, Pekka Enberg wrote:
> > > Hi Linus,
> > >
> > > Please consider pulling the latest LKVM tree from:
> > >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/penberg/linux.git kvmtool/for-linus
> > >
> > > LKVM is the long lost userspace friend of KVM that makes it really easy
> > > to launch virtualized Linx environment on x86 and PPC64 Linux.
> >
> > This still doesn't have any business in the kernel tree. [...]
>
> Pekka & the LKVM developers are using the tools/kvm/ tree setup
> to create new kernel features, to improve the kernel and to
> reuse kernel code, amongst other things.
>
> So being in the kernel tree is very practical and useful to
> them.
It's probably not a surprise to anyone that I'm with Ingo on this. It's
OK if people don't think tools/kvm is *worth it* but claiming that living
in a separate repository is just as easy is completely ignoring reality.
Pekka
next prev parent reply other threads:[~2012-10-18 10:31 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 11:34 Pekka Enberg
2012-10-12 17:27 ` Christoph Hellwig
2012-10-18 10:03 ` Ingo Molnar
2012-10-18 10:31 ` Pekka Enberg [this message]
2012-10-16 2:41 ` Stephen Rothwell
2012-10-16 14:50 ` Linus Torvalds
2012-10-20 7:04 ` Stephen Rothwell
2012-10-20 18:14 ` Borislav Petkov
2012-10-21 3:07 ` Dave Airlie
2012-10-21 3:46 ` Yinghai Lu
2012-10-21 11:03 ` Christoph Hellwig
2012-10-21 12:59 ` Ingo Molnar
2012-10-21 14:02 ` richard -rw- weinberger
2012-10-21 15:03 ` Ingo Molnar
2012-10-21 17:15 ` Borislav Petkov
2012-10-21 17:40 ` Markus Trippelsdorf
2012-10-21 17:51 ` Ingo Molnar
2012-10-21 17:54 ` Markus Trippelsdorf
2012-10-21 18:04 ` Markus Trippelsdorf
2012-10-21 18:10 ` Ingo Molnar
2012-10-22 9:26 ` Avi Kivity
2012-10-21 18:09 ` Ingo Molnar
2012-10-21 15:39 ` Pekka Enberg
2012-10-22 9:24 ` Avi Kivity
2012-10-22 10:16 ` Gleb Natapov
2012-10-23 2:20 ` Asias He
2012-10-31 15:05 ` Gleb Natapov
2012-10-21 11:18 ` Borislav Petkov
2012-10-21 11:29 ` richard -rw- weinberger
2012-10-21 22:16 ` Theodore Ts'o
2012-11-14 5:24 ` Stephen Rothwell
2012-11-14 6:02 ` Theodore Ts'o
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.2.02.1210181325460.9682@tux.localdomain \
--to=penberg@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=avi@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®