linux-kernel - Re: Add openrisc for-next branch to 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]

Message-ID: <alpine.LFD.2.20.1612010735330.29569@lianli.shorne-pla.net>
Date:   Thu, 1 Dec 2016 07:37:20 +0900 (JST)
From:   Stafford Horne <shorne@...il.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
cc:     Stafford Horne <shorne@...il.com>, linux-next@...r.kernel.org,
        linux-kernel@...r.kernel.org, openrisc@...ts.librecores.org
Subject: Re: Add openrisc for-next branch to linux-next



On Thu, 1 Dec 2016, Stephen Rothwell wrote:

> Hi Stafford,
>
> On Wed, 30 Nov 2016 22:22:41 +0900 (JST) Stafford Horne <shorne@...il.com> wrote:
>>
>> I have been working on getting the OpenRISC backlog of fixes sorted out
>> for upstream.  Can this branch be added to linux-next?
>>
>>    git://github.com/openrisc/linux.git for-next
>>
>> These have been through a few reviews and we plan to ask Linus to pull in
>> the next merge window.
>
> Added from today.
>
> Just a note: your top commits has no Signed-off-by from you as the committer ...

Hello,

Right I had been adding those as part of the `git send-email` phase but I 
realize I do need them in git now. Sorry about that.

> 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.

Thank You,

-Stafford