linux-kernel - Re: [PATCH] Remove support for score architecture

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]

Message-ID: <20130831194018.GM13318@ZenIV.linux.org.uk>
Date:	Sat, 31 Aug 2013 20:40:18 +0100
From:	Al Viro <viro@...IV.linux.org.uk>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	Guenter Roeck <linux@...ck-us.net>, linux-kernel@...r.kernel.org,
	Geert Uytterhoeven <geert@...ux-m68k.org>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Jiang Liu <jiang.liu@...wei.com>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"David S. Miller" <davem@...emloft.net>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Lennox Wu <lennox.wu@...il.com>,
	Chen Liqin <liqin.chen@...plusct.com>,
	Liqin Chen <liqin299@...il.com>
Subject: Re: [PATCH] Remove support for score architecture

On Sat, Aug 31, 2013 at 08:55:16PM +0200, Arnd Bergmann wrote:

> > Maybe this removal request is a bit early, but architecture support seems
> > to have vanished entirely. At the very least this puts interested parties
> > (if there are any) on notice.
> 
> AFAICT, this is the least maintained architecture we have at the moment,
> and your analysis is correct.
> 
> I think it can be removed unless we the maintainers have plans to become
> more active in the future or someone else steps up to maintain the
> architecture.

AFAICS, the architecture is stillborn - they planned to use it in game
consoles and stuff like that, but recession has hit the fan just as they
were about to do that.  Maintainers are not employed there anymore, gcc
had a commit updating maintainer address, but the new address is of
form ...+gcc@... and no corresponding update of address in the kernel
tree has happened.  In such situation I would really hesitate to put
the new address into MAINTAINERS...

IOW, this is an ex-parrot.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/