From: Sasha Levin <levinsasha928@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Avi Kivity <avi@redhat.com>, Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Pekka Enberg <penberg@kernel.org>,
linux-next@vger.kernel.org, Christoph Hellwig <hch@infradead.org>
Subject: Re: linux next: Native Linux KVM tool inclusion request
Date: Wed, 24 Aug 2011 07:33:11 +0300 [thread overview]
Message-ID: <1314160391.3449.0.camel@lappy> (raw)
In-Reply-To: <20110824115233.4b515a6ceee8910e9c21fc50@canb.auug.org.au>
On Wed, 2011-08-24 at 11:52 +1000, Stephen Rothwell wrote:
> Hi Sasha,
>
> On Mon, 22 Aug 2011 23:29:20 +0300 Sasha Levin <levinsasha928@gmail.com> wrote:
> >
> > I would like to ask you to include the Native Linux KVM tool in the
> > linux-next tree.
> >
> > The branch is named 'master' and is located in:
> >
> > git://github.com/penberg/linux-kvm.git
>
> I have included your tree from today and called it "kvmtool". I have you
> and Pekka currently listed as teh contacts (since it looks like it is his
> tree on github). Please consider adding a MAINTAINERS entry for this.
>
> Thanks for adding your subsystem tree as a participant of linux-next. As
> you may know, this is not a judgment of your code. The purpose of
> linux-next is for integration testing and to lower the impact of
> conflicts between subsystems in the next merge window.
>
> You will need to ensure that the patches/commits in your tree/series have
> been:
> * submitted under GPL v2 (or later) and include the Contributor's
> Signed-off-by,
> * posted to the relevant mailing list,
> * reviewed by you (or another maintainer of your subsystem tree),
> * successfully unit tested, and
> * destined for the current or next Linux merge window.
>
> Basically, this should be just what you would send to Linus (or ask him
> to fetch). It is allowed to be rebased if you deem it necessary.
>
Thank you for the inclusion.
We will add a MAINTAINERS file.
--
Sasha.
prev parent reply other threads:[~2011-08-24 4:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-22 20:29 linux next: Native Linux KVM tool inclusion request Sasha Levin
2011-08-23 0:39 ` Christoph Hellwig
2011-08-23 5:08 ` Pekka Enberg
2011-08-23 6:58 ` Stephen Rothwell
2011-08-23 7:02 ` Pekka Enberg
2011-08-24 8:31 ` Avi Kivity
2011-08-24 9:19 ` Pekka Enberg
2011-08-24 9:33 ` Avi Kivity
2011-08-24 9:38 ` Pekka Enberg
2011-08-24 1:52 ` Stephen Rothwell
2011-08-24 4:33 ` Sasha Levin [this message]
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=1314160391.3449.0.camel@lappy \
--to=levinsasha928@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=avi@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@kernel.org \
--cc=sfr@canb.auug.org.au \
--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;
as well as URLs for NNTP newsgroup(s).