linux-kernel - Re: Please include Aspeed ARM SoC tree in 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:   Thu, 12 Jan 2017 08:17:15 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Joel Stanley <joel@....id.au>
Cc:     linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
        Benjamin Herrenschmidt <benh@...nel.crashing.org>,
        Andrew Jeffery <andrew@...id.au>,
        Cédric Le Goater <clg@...d.org>,
        Olof Johansson <olof@...om.net>, Arnd Bergmann <arnd@...db.de>
Subject: Re: Please include Aspeed ARM SoC tree in linux-next

Hi Joel,

On Wed, 11 Jan 2017 12:11:29 +1100 Joel Stanley <joel@....id.au> wrote:
>
> I'm the maintainer for the Aspeed ARM SoC tree and I would like it
> added to linux-next.
> 
> The tree is a sub-maintainer tree for the Aspeed family of 32-bit ARM
> SoCs that went upstream earlier last year.
> 
> Tree: git://git.kernel.org/pub/scm/linux/kernel/git/joel/aspeed.git
> Branch: for-next
> 
> for-next is a merge of the trees that I intend to send to the ARM
> maintainers for 4.11.
> 
> For now please notify just myself if something breaks.

Added from today.

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgement 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