-----Original Message-----
From: linux-next-owner@vger.kernel.org [mailto:linux-next-owner@vger.kernel.org] On Behalf Of Stephen Rothwell
Sent: Tuesday, February 01, 2011 6:39 AM
To: Xuetao Guan
Cc: dmitry.torokhov@gmail.com; arnd@arndb.de; gregkh@suse.de; dtor@mail.ru; jbarnes@virtuousgeek.org; linux-
next@vger.kernel.org; linux-kernel@vger.kernel.org
Subject: Re: Request (2nd) for unicore32 architecture codes to merge into linux-next

Hi,

On Sat, 22 Jan 2011 21:52:11 +0800 Xuetao Guan [off-list ref] wrote:

quoted

I want to merge unicore32 repo into linux-next tree, the position is
(unicore32 branch):
  git://git.kernel.org/pub/scm/linux/kernel/git/epip/linux-2.6-unicore32.git

Included from next-20110131.

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

Thanks.

Guan Xuetao