linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: stand-alone kvmtool
Date: Wed, 25 Feb 2015 12:16:11 +0000	[thread overview]
Message-ID: <20150225121610.GA12377@arm.com> (raw)
In-Reply-To: <54EB622E.3020700@iki.fi>

On Mon, Feb 23, 2015 at 05:23:58PM +0000, Pekka Enberg wrote:
> Hi,

Hi Pekka,

Sorry for the delay, I've been away from email for a few days.

> On 2/18/15 5:50 PM, Will Deacon wrote:
> > Thanks for doing this. Since it looks unlikely that kvmtool will ever be
> > merged back into the kernel tree, it makes sense to cut the dependency
> > in my opinion.
> 
> I am certainly OK with a standalone repository which preserves the 
> history. Will, would you like to take over the proposed new repository 
> and put it somewhere on git.kernel.org, perhaps?

Sure thing. I'll sync-up with Andre and reply back here when we've got
something sensible.

One extra point that I don't think has been mentioned in this thread so
far is that separating kvmtool from the kernel sources is likely a
prerequisite for distribution packaging. Once we've got something sorted
out, I'll poke some friendly local debian developers and see if they can't
package it up for us.

Will

  reply	other threads:[~2015-02-25 12:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-13 10:39 stand-alone kvmtool Andre Przywara
2015-02-13 14:30 ` Claudio Fontana
2015-02-13 14:40   ` Andre Przywara
2015-02-13 16:36     ` Claudio Fontana
2015-02-18 15:50 ` Will Deacon
2015-02-23 10:11   ` Andre Przywara
2015-02-26 11:02     ` Alex Bennée
2015-03-01 10:21       ` Pekka Enberg
2015-02-23 17:23   ` Pekka Enberg
2015-02-25 12:16     ` Will Deacon [this message]
2015-06-03 17:04     ` Will Deacon
2015-02-19 10:56 ` Sasha Levin
2015-02-23 11:12   ` Andre Przywara
2015-02-23 12:14   ` Russell King - ARM Linux
2015-02-23 14:27   ` Christoffer Dall

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=20150225121610.GA12377@arm.com \
    --to=will.deacon@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).