linux-kernel - Re: [PATCH 0/1] About MIPS/Loongson maintainance

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] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 8 Dec 2017 07:51:35 +0000
From:   James Hogan <james.hogan@...s.com>
To:     Jiaxun Yang <jiaxun.yang@...goat.com>
CC:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Huacai Chen <chenhc@...ote.com>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        "Stephen Rothwell" <sfr@...b.auug.org.au>,
        Ralf Baechle <ralf@...ux-mips.org>,
        Rui Wang <wangr@...ote.com>, Binbin Zhou <zhoubb@...ote.com>,
        Ce Sun <sunc@...ote.com>, Yao Wang <wangyao@...ote.com>,
        Liangliang Huang <huangll@...ote.com>,
        Fuxin Zhang <zhangfx@...ote.com>,
        Zhangjin Wu <wuzhangjin@...il.com>, <r@....cc>,
        <zhoubb.aaron@...il.com>, <huanglllzu@....com>, <513434146@...com>,
        <1393699660@...com>, <linux-mips@...ux-mips.org>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/1] About MIPS/Loongson maintainance

On Fri, Dec 08, 2017 at 12:01:46PM +0800, Jiaxun Yang wrote:
> Also we're going to separate code between
> Loongson2 and Loongson3 since they are becoming more and more
> identical.

Do you mean you want to combine them?

> But It will cause a lot of changes under march of loongson64
>  that currently maintaining by linux-mips community. Send plenty of
> patches to mailing list would not be a wise way to do that. So we can
> PR these changes to linux-next directly and PR to linux-mips before
> merge window.

For the avoidance of doubt, a pull request would not excempt you from
needing your patches properly reviewed on the mailing lists first.

And quoting Stephen's boilerplate response to linux-next additions:
> 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
James

Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)