From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Huacai Chen <chenhc@lemote.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Ralf Baechle <ralf@linux-mips.org>,
James Hogan <james.hogan@mips.com>, 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>,
Jiaxun Yang <jiaxun.yang@flygoat.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: Thu, 7 Dec 2017 07:57:59 +0100 [thread overview]
Message-ID: <20171207065759.GC19722@kroah.com> (raw)
In-Reply-To: <1512628268-18357-1-git-send-email-chenhc@lemote.com>
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?
> 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?
thanks,
greg k-h
next prev parent reply other threads:[~2017-12-07 6:57 UTC|newest]
Thread overview: 12+ 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 ` Greg Kroah-Hartman [this message]
2017-12-07 9:28 ` [PATCH 0/1] About MIPS/Loongson maintainance Jiaxun Yang
2017-12-07 11:05 ` James Hogan
2017-12-07 13:10 ` Jiaxun Yang
2017-12-07 14:18 ` James Hogan
2017-12-08 4:01 ` Jiaxun Yang
2017-12-08 7:51 ` James Hogan
2017-12-08 9:00 ` Huacai Chen
2017-12-08 9:34 ` Jiaxun Yang
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=20171207065759.GC19722@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=1393699660@qq.com \
--cc=513434146@qq.com \
--cc=chenhc@lemote.com \
--cc=huangll@lemote.com \
--cc=huanglllzu@163.com \
--cc=james.hogan@mips.com \
--cc=jiaxun.yang@flygoat.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