From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Stefano Stabellini <stefano.stabellini@eu•citrix.com>
Cc: Jeremy Fitzhardinge <Jeremy.Fitzhardinge@citrix•com>,
Stefano Stabellini <Stefano.Stabellini@eu•citrix.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle•com>,
"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>,
Chris Wright <chrisw@sous-sol•org>,
"virtualization@lists•osdl.org" <virtualization@lists•osdl.org>,
"linux-next@vger•kernel.org" <linux-next@vger•kernel.org>,
Andrew Morton <akpm@linux-foundation•org>,
"xen-devel@lists•xensource.com" <xen-devel@lists•xensource.com>
Subject: Re: xen PV on HVM and initial domain merge in linux-next
Date: Thu, 21 Oct 2010 10:45:41 +1100 [thread overview]
Message-ID: <20101021104541.8e10159a.sfr@canb.auug.org.au> (raw)
In-Reply-To: <alpine.DEB.2.00.1010201644380.10348@kaball-desktop>
[-- Attachment #1.1: Type: text/plain, Size: 2019 bytes --]
Hi Stefano,
On Wed, 20 Oct 2010 16:47:51 +0100 Stefano Stabellini <stefano.stabellini@eu•citrix.com> wrote:
>
> Good idea, I have created a link called linux-next to
> 2.6.36-rc8-initial-domain-v5 so the following should also work:
>
> git://xenbits.xen.org/people/sstabellini/linux-pvhvm.git linux-next
I have added that branch from today with just you listed as the contact
(if you ant anyone else (even a mailing list) listed as a contact, just
let me know.
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.
--
Cheers,
Stephen Rothwell
sfr@canb•auug.org.au
Legal Stuff:
By participating in linux-next, your subsystem tree contributions are
public and will be included in the linux-next trees. You may be sent
e-mail messages indicating errors or other issues when the
patches/commits from your subsystem tree are merged and tested in
linux-next. These messages may also be cross-posted to the linux-next
mailing list, the linux-kernel mailing list, etc. The linux-next tree
project and IBM (my employer) make no warranties regarding the linux-next
project, the testing procedures, the results, the e-mails, etc. If you
don't agree to these ground rules, let me know and I'll remove your tree
from participation in linux-next.
[-- Attachment #1.2: Type: application/pgp-signature, Size: 490 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists•xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-10-20 23:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.2.00.1010191254460.2423@kaball-desktop>
2010-10-19 17:51 ` xen PV on HVM and initial domain merge in linux-next Stefano Stabellini
2010-10-20 0:32 ` Stephen Rothwell
2010-10-20 15:11 ` [Xen-devel] " Dan Magenheimer
2010-10-20 16:43 ` Chris Wright
2010-10-20 15:16 ` Stefano Stabellini
2010-10-20 15:28 ` Konrad Rzeszutek Wilk
2010-10-20 15:47 ` Stefano Stabellini
2010-10-20 23:45 ` Stephen Rothwell [this message]
2010-10-21 13:44 ` Stefano Stabellini
2010-10-20 15:45 ` Jeremy Fitzhardinge
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=20101021104541.8e10159a.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=Jeremy.Fitzhardinge@citrix$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=chrisw@sous-sol$(echo .)org \
--cc=konrad.wilk@oracle$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=stefano.stabellini@eu$(echo .)citrix.com \
--cc=virtualization@lists$(echo .)osdl.org \
--cc=xen-devel@lists$(echo .)xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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