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
Attachment:
signature.asc
Description: This is a digitally signed message part
