Messages in this thread | | | Date | Sat, 22 Feb 2020 11:41:24 +0100 | From | Thomas Bogendoerfer <> | Subject | Re: [PATCH 2/2] MAINTAINERS: Set MIPS status to Odd Fixes |
| |
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 ]
| |