Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Jiaxun Yang <jiaxun.yang@flygoat.com>
To: James Hogan <james.hogan@mips.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Huacai Chen <chenhc@lemote.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Ralf Baechle <ralf@linux-mips.org>, Rui Wang <wangr@lemote.com>,
	Binbin Zhou <zhoubb@lemote.com>, Ce Sun <sunc@lemote.com>,
	Yao Wang <wangyao@lemote.com>,
	Liangliang Huang <huangll@lemote.com>,
	Fuxin Zhang <zhangfx@lemote.com>,
	Zhangjin Wu <wuzhangjin@gmail.com>,
	r@hev.cc, zhoubb.aaron@gmail.com, huanglllzu@163.com,
	513434146@qq.com, 1393699660@qq.com, linux-mips@linux-mips.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/1] About MIPS/Loongson maintainance
Date: Fri, 08 Dec 2017 17:34:30 +0800	[thread overview]
Message-ID: <1512725670.1852.15.camel@flygoat.com> (raw)
In-Reply-To: <20171208075134.GP5027@jhogan-linux.mipstec.com>

On 2017-12-08 Fri 07:51 +0000,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?

Sorry, my fault. They're become more and more different and  I'm going
to separate loongson64 into loongson2 and loongson3.

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

So we can commit by ourselves after subsystem's review to reduce linux-
mips's workload. 
Since Huacai Chen said that we won't send PR, maybe it's unnecessary.
Thanks.

> 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
-- 
Jiaxun Yang

      parent reply	other threads:[~2017-12-08  9:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-07  6:31 [PATCH 0/1] About MIPS/Loongson maintainance Huacai Chen
2017-12-07  6:31 ` [PATCH 1/1] MAINTAINERS: Add Loongson-2/Loongson-3 maintainers Huacai Chen
2018-02-01 11:52   ` James Hogan
2017-12-07  6:57 ` [PATCH 0/1] About MIPS/Loongson maintainance Greg Kroah-Hartman
2017-12-07  9:28   ` Jiaxun Yang
2017-12-07 11:05   ` James Hogan
2017-12-07 11:05     ` James Hogan
2017-12-07 13:10     ` Jiaxun Yang
2017-12-07 14:18       ` James Hogan
2017-12-07 14:18         ` James Hogan
2017-12-08  4:01         ` Jiaxun Yang
2017-12-08  7:51           ` James Hogan
2017-12-08  7:51             ` James Hogan
2017-12-08  9:00             ` Huacai Chen
2017-12-08  9:34             ` Jiaxun Yang [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1512725670.1852.15.camel@flygoat.com \
    --to=jiaxun.yang@flygoat.com \
    --cc=1393699660@qq.com \
    --cc=513434146@qq.com \
    --cc=chenhc@lemote.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=huangll@lemote.com \
    --cc=huanglllzu@163.com \
    --cc=james.hogan@mips.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=r@hev.cc \
    --cc=ralf@linux-mips.org \
    --cc=sfr@canb.auug.org.au \
    --cc=sunc@lemote.com \
    --cc=torvalds@linux-foundation.org \
    --cc=wangr@lemote.com \
    --cc=wangyao@lemote.com \
    --cc=wuzhangjin@gmail.com \
    --cc=zhangfx@lemote.com \
    --cc=zhoubb.aaron@gmail.com \
    --cc=zhoubb@lemote.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox