From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: YunQiang Su <wzssyqa@gmail.com>
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>
Subject: Re: [PATCH 2/2] MAINTAINERS: Set MIPS status to Odd Fixes
Date: Sat, 22 Feb 2020 11:41:24 +0100 [thread overview]
Message-ID: <20200222104124.GA4589@alpha.franken.de> (raw)
In-Reply-To: <CAKcpw6UDik=K6MdEayDPVaZP+BsqrbKoKAXJaHLERrxDmFF7+A@mail.gmail.com>
On Thu, Feb 20, 2020 at 08:11:08PM +0800, YunQiang Su wrote:
> 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.
sure, it would be helpfull. And with a reasonable price I have no problem
buying a new machine. But IMHO it's not mandatory for a maintainer
to have all supported hardware available.
> 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?
Looking at the number of patches in arch/mips for the last few
release cylces we were always in the range of 100-150 commits.
So I don't see a need for a co-maintainer, but having backup
maintainer(s) is a good thing.
For me maintaining means
- keep MIPS archicture alive (legacy and newer stuff)
- collecting patches and integrating them into a git tree for pulling
- send pull requests to Linus in a timely manner
- review/comment patches
- give guidance on how to do abstractions inside MIPS arch code
Some personal background
- doing Linux/MIPS coding since 1995
- worked as system architect for OS development with MIPS 4kec, 24k, 34k
based embedded systems
- working now for SUSE in kernel network driver area (with enough time
for other open source projects)
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-22 10:41 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
2020-02-20 17:01 ` YunQiang Su
2020-02-20 17:36 ` Zhou Yanjie
2020-02-22 10:41 ` Thomas Bogendoerfer [this message]
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=20200222104124.GA4589@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=chris.wang@neocore.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=paulburton@kernel.org \
--cc=wayne.sun@cipunited.com \
--cc=wzssyqa@gmail.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).