[Top] [All Lists]

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

To: James Hogan <>
Subject: Re: [PATCH 0/1] About MIPS/Loongson maintainance
From: Huacai Chen <>
Date: Fri, 8 Dec 2017 17:00:46 +0800
Cc: Jiaxun Yang <>, Greg Kroah-Hartman <>, Linus Torvalds <>, Stephen Rothwell <>, Ralf Baechle <>, Rui Wang <>, Binbin Zhou <>, Ce Sun <>, Yao Wang <>, Liangliang Huang <>, Fuxin Zhang <>, Zhangjin Wu <>, 王锐 <>, Aaron Chou <>,,, David king <>, Linux MIPS Mailing List <>,
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=KxDuJ5sn1MJJg67AjOYxyEANW4HDk4OjvU/U77NB870=; b=vUpBfrn7aK3sNRbaVyNuUlh6fIZDOKhQLDtOKe+Wha0S6NJmhjmR/uhCwqcOJEDpmT SvvjYhsT1veLg/8VMlIPjFqjeTl27stxRzxzG6nUE9LttymLkIh7x7ppRiDsX21qPEGG k7D6Us2zaP10ib0T3emsTPEf7fp0KdWBZ9k19kGcKJU3/QB5XXmN6tZHnsplOe9LaCWg 6Bt/rNKnFXYNZo6tQibLHcXqwihPm4f/emq6glQBkbIja2ujh8bkcjQdm4E2Szmsd/m4 M0k4POEXJpBhXPznXBvawx7PR5R46v0BRon8fC8MG/vA0HcqUbdxxF2tXW3Y/pSS0I8N s9lQ==
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: <> <> <> <> <> <> <>
Hi, James,

Of course we don't want to send PR directly, if there is a better way.
So, I hope you can officially be a co-maintainer of linux-mips, and as
a result, our community will become more active. I think most of MIPS
developers have the same will as me.


On Fri, Dec 8, 2017 at 3:51 PM, James Hogan <> wrote:
> 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

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