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:   Thu, 07 Dec 2017 17:28:54 +0800
From:   Jiaxun Yang <jiaxun.yang@...goat.com>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Huacai Chen <chenhc@...ote.com>
Cc:     Linus Torvalds <torvalds@...ux-foundation.org>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        Ralf Baechle <ralf@...ux-mips.org>,
        James Hogan <james.hogan@...s.com>,
        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 2017-12-07 07:57 +0100，Greg Kroah-Hartman wrote：
> On Thu, Dec 07, 2017 at 02:31:07PM +0800, Huacai Chen wrote:
> > Hi, Linus, Stephen, Greg, Ralf and James,
> > 
> > We are kernel developers from Lemote Inc. and Loongson community.
> > We
> > have already made some contributions in Linux kernel, but we hope
> > we
> > can do more works.
> > 
> > Of course Loongson is a sub-arch in MIPS, but linux-mips community
> > is
> > so inactive (Maybe maintainers are too busy?) that too many patches
> > (
> > Not only for Loongson, but also for other sub-archs) were delayed
> > for
> > a long time. So we are seeking a more efficient way to make
> > Loongson
> > patches be merged in upstream.
> > 
> > Now we have a github organization for collaboration:
> > https://github.com/linux-loongson/linux-loongson.git
> 
> Ick, why not get a kernel.org account for your git tree?

Of course we would like to get a kernel.org account. But in order to
get a kernel.org account, we must have enough kernel developer's PGP
sigs. In mainland China, it's hard to meet any of them. So wo choose
GitHub to host our git tree.
 
> 
> > We don't want to replace linux-mips, we just want to find a way to
> > co-
> > operate with linux-mips. So we will still use the maillist and
> > patchwork
> > of linux-mips, but we hope we can send pull requests from our
> > github to
> > linux-next and linux-mainline by ourselves (if there is no
> > objections
> > to our patches from linux-mips community).
> 
> What does the mips maintainers think about this?
> 
> Odds are a linux-next tree is fine, but they probably want to merge
> the
> trees into their larger mips one for the pulls to Linus, much like
> the
> arm-core tree works, right?
Yeah, thanks for your suggestion, we can do like this to reduce work
load of Linus.
> 
> thanks,
> 
> greg k-h

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