[Top] [All Lists]

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

To: Huacai Chen <>
Subject: Re: [PATCH 0/1] About MIPS/Loongson maintainance
From: Greg Kroah-Hartman <>
Date: Thu, 7 Dec 2017 07:57:59 +0100
Cc: Linus Torvalds <>, Stephen Rothwell <>, Ralf Baechle <>, James Hogan <>, Rui Wang <>, Binbin Zhou <>, Ce Sun <>, Yao Wang <>, Liangliang Huang <>, Fuxin Zhang <>, Zhangjin Wu <>, Jiaxun Yang <>,,,,,,,
In-reply-to: <>
List-archive: <>
List-help: <>
List-id: linux-mips <>
List-owner: <>
List-post: <>
List-software: Ecartis version 1.0.0
List-subscribe: <>
List-unsubscribe: <>
Original-recipient: rfc822;
References: <>
User-agent: Mutt/1.9.1 (2017-09-22)
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:

Ick, why not get a account for your 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?


greg k-h

<Prev in Thread] Current Thread [Next in Thread>