lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 20 Feb 2020 20:11:08 +0800
From:   YunQiang Su <wzssyqa@...il.com>
To:     Thomas Bogendoerfer <tsbogend@...ha.franken.de>
Cc:     Paul Burton <paulburton@...nel.org>,
        linux-mips <linux-mips@...r.kernel.org>,
        linux-kernel@...r.kernel.org, wayne.sun@...united.com,
        chris.wang@...core.cn, Yunqiang Su <ysu@...ecomp.com>
Subject: Re: [PATCH 2/2] MAINTAINERS: Set MIPS status to Odd Fixes

CC people from NeoCore and CIP United, and my Wave Computing's mail address.

Thomas Bogendoerfer <tsbogend@...ha.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.

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 ]



-- 
YunQiang Su

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ