lkml.org 
[lkml]   [2011]   [Feb]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectFW: Request (2nd) for unicore32 architecture codes to merge into linux-next
Date
Linus:
Due to helps from many kindly peoples, unicore32 branch could be a candidate to merge into linux kernel.
The position is (unicore32 branch):
git://git.kernel.org/pub/scm/linux/kernel/git/epip/linux-2.6-unicore32.git
which had been integration tested from linux-next-20110131.

Signed-off-by: Guan Xuetao <gxt@mprc.pku.edu.cn>

Guan Xuetao

> -----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 <epip.guan@gmail.com> wrote:
> >
> > 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
>
> 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.



\
 
 \ /
  Last update: 2011-02-01 06:19    [W:0.059 / U:4.528 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site