All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@iki.fi>
To: Will Deacon <will.deacon@arm.com>,
	Andre Przywara <andre.przywara@arm.com>
Cc: Cyrill Gorcunov <gorcunov@gmail.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	Marc Zyngier <Marc.Zyngier@arm.com>,
	Asias He <asias.hejun@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Pekka Enberg <penberg@kernel.org>,
	Ronald Minnich <rminnich@google.com>,
	Sasha Levin <sasha.levin@oracle.com>,
	"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: stand-alone kvmtool
Date: Mon, 23 Feb 2015 19:23:58 +0200	[thread overview]
Message-ID: <54EB622E.3020700@iki.fi> (raw)
In-Reply-To: <20150218155042.GF22017@arm.com>

Hi,

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?

- Pekka

WARNING: multiple messages have this Message-ID (diff)
From: penberg@iki.fi (Pekka Enberg)
To: linux-arm-kernel@lists.infradead.org
Subject: stand-alone kvmtool
Date: Mon, 23 Feb 2015 19:23:58 +0200	[thread overview]
Message-ID: <54EB622E.3020700@iki.fi> (raw)
In-Reply-To: <20150218155042.GF22017@arm.com>

Hi,

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?

- Pekka

WARNING: multiple messages have this Message-ID (diff)
From: Pekka Enberg <penberg@iki.fi>
To: Will Deacon <will.deacon@arm.com>,
	Andre Przywara <andre.przywara@arm.com>
Cc: Pekka Enberg <penberg@kernel.org>,
	Sasha Levin <sasha.levin@oracle.com>,
	Cyrill Gorcunov <gorcunov@gmail.com>,
	Asias He <asias.hejun@gmail.com>,
	"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Marc Zyngier <Marc.Zyngier@arm.com>,
	Ronald Minnich <rminnich@google.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: stand-alone kvmtool
Date: Mon, 23 Feb 2015 19:23:58 +0200	[thread overview]
Message-ID: <54EB622E.3020700@iki.fi> (raw)
In-Reply-To: <20150218155042.GF22017@arm.com>

Hi,

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?

- Pekka

  parent reply	other threads:[~2015-02-23 17:18 UTC|newest]

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

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=54EB622E.3020700@iki.fi \
    --to=penberg@iki.fi \
    --cc=Marc.Zyngier@arm.com \
    --cc=andre.przywara@arm.com \
    --cc=asias.hejun@gmail.com \
    --cc=gorcunov@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@kernel.org \
    --cc=rminnich@google.com \
    --cc=sasha.levin@oracle.com \
    --cc=will.deacon@arm.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.