linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhou Yanjie <zhouyanjie@wanyeetech.com>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>,
	Huacai Chen <chenhuacai@gmail.com>,
	"open list:MIPS" <linux-mips@vger.kernel.org>
Cc: Paul Burton <paulburton@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>, ysu <ysu@wavecomp.com>,
	Paul Cercueil <paul@crapouillou.net>
Subject: Re: [PATCH 2/2] MAINTAINERS: Set MIPS status to Odd Fixes
Date: Thu, 20 Feb 2020 18:06:32 +0800	[thread overview]
Message-ID: <5E4E5A28.4090804@wanyeetech.com> (raw)
In-Reply-To: <17061a9f690.e5cbd01f5685.8497926865164942268@flygoat.com>

Hi,

I think Huacai Chen and Paul Cercueil are also two potential candidates 
for the maintainer.
Both of them have been active  for many years and have contributed a lot 
of code to MIPS.

Thanks and best regards!

On 2020年02月20日 16:14, Jiaxun Yang wrote:
>
> 于 2020年2月20日 GMT+08:00 下午2:44:03, Huacai Chen <chenhuacai@gmail.com> 写到:
>> Hi, all,
>>
>> I suggest Jiaxun Yang to be the new Linux/MIPS maintainer because of
>> the following reasons:
>>
>> 1. He is familiar with Linux kernel & MIPS architecture.
>> 2. He is active and has already contributed many patches.
>> 3. He is not an employee of any corporation, so people can expect him
>> to be neutral.
>> 4. He is young and has enough free time to follow the mainstream
>> development closely.
>> 5. His English is good and is willing to maintain a good level of
>> communication with other contributors.
>>
>> Jiaxun, what's your opinion?
> Resend as MIPS List rejected the previous mail.
>
> Thanks for your recommendation.
>
> It's my pleasure to take this duty if I'm eligible.
>
> I have experience in MIPS chips and have already involved in some review processes.
> i.e.loongson, Ingenic/MediaTek & etc.
>
> As what Huacai has said, I'm a pure contributor from community,
> which means I will able to be neutral to MIPS family members.
>
> [Also added Yunqiang Su to Cc list as he is the
> only current MIPS company employee I know.]
>
> Thanks.
>> Regards,
>> Huacai Chen


  reply	other threads:[~2020-02-20 10:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-20  8:14 [PATCH 2/2] MAINTAINERS: Set MIPS status to Odd Fixes Jiaxun Yang
2020-02-20 10:06 ` Zhou Yanjie [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-02-19 19:17 [PATCH 0/2] MAINTAINERS: Update MIPS entry Paul Burton
2020-02-19 19:17 ` [PATCH 2/2] MAINTAINERS: Set MIPS status to Odd Fixes Paul Burton
2020-02-20  3:08   ` Joe Perches
2020-02-20  6:44     ` Huacai Chen
2020-02-20  7:55       ` Jiaxun Yang
2020-02-20 11:23   ` Thomas Bogendoerfer
2020-02-20 12:11     ` YunQiang Su
2020-02-20 12:40       ` Zhou Yanjie
2020-02-20 17:01         ` YunQiang Su
2020-02-20 17:36           ` Zhou Yanjie
2020-02-22 10:41       ` Thomas Bogendoerfer
2020-02-22 16:08   ` Paul Cercueil
2020-02-22 17:54     ` Jiaxun Yang
2020-02-24  8:37     ` Philippe Mathieu-Daudé
2020-02-24 13:50       ` Paul Cercueil
2020-02-24 10:53     ` Thomas Bogendoerfer

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=5E4E5A28.4090804@wanyeetech.com \
    --to=zhouyanjie@wanyeetech.com \
    --cc=chenhuacai@gmail.com \
    --cc=jiaxun.yang@flygoat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=paul@crapouillou.net \
    --cc=paulburton@kernel.org \
    --cc=ysu@wavecomp.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;
as well as URLs for NNTP newsgroup(s).