Re: [PATCH 00/18] Make the big kernel lock optional

From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Matt, linux-sh@vger.kernel.org,
	Roman Zippel <zippel@linux-m68k.org>,
	linux-pci@vger.kernel.org,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	Picco <bob.picco@hp.com>, Jaroslav Kysela <perex@perex.cz>,
	netdev@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
	linux-s390@vger.kernel.org,
	Jesper Nilsson <jesper.nilsson@axis.com>,
	Mark Gross <mark.gross@intel.com>, Helge Deller <deller@gmx.de>,
	"James E.J. Bottomley" <jejb@parisc-linux.org>,
	Uytterhoeven <geert@linux-m68k.org>,
	Karsten, Geert, Ingo Molnar <mingo@elte.hu>,
	linux-media@vger.kernel.org,
	user-mode-linux-devel@lists.sourceforge.net,
	Clemens Ladisch <clemens@ladisch.de>,
	Jeff Dike <jdike@addtoit.com>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	Mikael Starvik <starvik@axis.com>, Tejun Heo <tj@kernel.org>,
	linux-m68k@lists.linux-m68k.org,
	Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
	Jesse Barnes <jbarnes@vi
Subject: Re: [PATCH 00/18] Make the big kernel lock optional
Date: Wed, 15 Sep 2010 19:37:18 +1000	[thread overview]
Message-ID: <20100915193718.3117b7bb.sfr@canb.auug.org.au> (raw)
In-Reply-To: <1284492909-7147-1-git-send-email-arnd@arndb.de>

[-- Attachment #1.1: Type: text/plain, Size: 1739 bytes --]

On Tue, 14 Sep 2010 21:34:51 +0200 Arnd Bergmann <arnd@arndb.de> wrote:
>
> Stephen, please add
> git+ssh://master.kernel.org/pub/scm/linux/kernel/git/arnd/bkl.git config

Added from today.

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: 276 bytes --]

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev

[-- Attachment #3: Type: text/plain, Size: 194 bytes --]

_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel