From: Zhou Yanjie <zhouyanjie@wanyeetech.com>
To: YunQiang Su <wzssyqa@gmail.com>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: Paul Burton <paulburton@kernel.org>,
linux-mips <linux-mips@vger.kernel.org>,
linux-kernel@vger.kernel.org, wayne.sun@cipunited.com,
chris.wang@neocore.cn, Yunqiang Su <ysu@wavecomp.com>,
dongsheng.qiu@ingenic.com, xuwanhao@wanyeetech.com
Subject: Re: [PATCH 2/2] MAINTAINERS: Set MIPS status to Odd Fixes
Date: Thu, 20 Feb 2020 20:40:30 +0800 [thread overview]
Message-ID: <5E4E7E3E.6070608@wanyeetech.com> (raw)
In-Reply-To: <CAKcpw6UDik=K6MdEayDPVaZP+BsqrbKoKAXJaHLERrxDmFF7+A@mail.gmail.com>
Hi,
CC people from Ingenic Semi and Wanyee Tech.
On 2020年02月20日 20:11, YunQiang Su wrote:
> CC people from NeoCore and CIP United, and my Wave Computing's mail address.
>
> Thomas Bogendoerfer <tsbogend@alpha.franken.de> 于2020年2月20日周四 下午7:23写道：
>> On Wed, Feb 19, 2020 at 11:17:30AM -0800, Paul Burton wrote:
>>> My time with MIPS the company has reached its end, and so at best I'll
>>> have little time spend on maintaining arch/mips/. Reflect that in
>>> MAINTAINERS by changing status to Odd Fixes. Hopefully this might spur
>>> the involvement of someone with more time, but even if not it should
>>> help serve to avoid unrealistic expectations.
>> I'd like to jump in as MIPS maintainer. I'm doing Linux MIPS kernel
> It is a great news that you are willing to act as maintainer as Linux-MIPS.
>
>> development since ages (started with an Olivetti M700 and kernel version
>> 2.x) and right now time for doing the jobs isn't issue:-)
>>
> I noticed that you are mainly working some old machines.
> And recently years, there are some new machines from Ingenic, Loongson, MTK etc.
> MIPS Inc also have some MIPSr6 IPs.
> I think that you need some of these machines.
I can provide some new Ingenic platform machines as a gift to Thomas.
Ingenic X1000 can be provided in a short time, it has been directly
supported by kernel 5.6.
X1830 and X2000 will be available later.
> In the last years, we see that the single maintainer is not enough as people may
> quite busy.
> Do you think that we need co-maintainers?
>
>> Thomas.
>>
>> --
>> Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
>> good idea. [ RFC1925, 2.3 ]
>
>
next prev parent reply other threads:[~2020-02-20 12:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 19:17 [PATCH 0/2] MAINTAINERS: Update MIPS entry Paul Burton
2020-02-19 19:17 ` [PATCH 1/2] MAINTAINERS: Remove Ralf Baechle as MIPS maintainer 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2020-02-20 8:14 Jiaxun Yang
2020-02-20 10:06 ` Zhou Yanjie
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=5E4E7E3E.6070608@wanyeetech.com \
--to=zhouyanjie@wanyeetech.com \
--cc=chris.wang@neocore.cn \
--cc=dongsheng.qiu@ingenic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=paulburton@kernel.org \
--cc=tsbogend@alpha.franken.de \
--cc=wayne.sun@cipunited.com \
--cc=wzssyqa@gmail.com \
--cc=xuwanhao@wanyeetech.com \
--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).