linux-kernel - FW: Request (2nd) for unicore32 architecture codes to merge into linux-next

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 1 Feb 2011 13:14:56 +0800
From:	"Guan Xuetao" <gxt@...c.pku.edu.cn>
To:	"'Linus Torvalds'" <torvalds@...ux-foundation.org>
Cc:	<sfr@...b.auug.org.au>,
	"'Andrew Morton'" <akpm@...ux-foundation.org>,
	"Arnd Bergmann" <arnd@...db.de>, <gregkh@...e.de>,
	<linux-kernel@...r.kernel.org>
Subject: FW: Request (2nd) for unicore32 architecture codes to merge into linux-next

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@...c.pku.edu.cn>

Guan Xuetao

> -----Original Message-----
> From: linux-next-owner@...r.kernel.org [mailto:linux-next-owner@...r.kernel.org] On Behalf Of Stephen Rothwell
> Sent: Tuesday, February 01, 2011 6:39 AM
> To: Xuetao Guan
> Cc: dmitry.torokhov@...il.com; arnd@...db.de; gregkh@...e.de; dtor@...l.ru; jbarnes@...tuousgeek.org; linux-
> next@...r.kernel.org; linux-kernel@...r.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@...il.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@...b.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.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/