linux-kernel - Re: [PATCH 5/7] openrisc: Support both old (or32) and new (or1k) toolchain

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: <alpine.LFD.2.20.1609191807160.2352@lianli.shorne-pla.net>
Date:   Mon, 19 Sep 2016 18:11:34 +0900 (JST)
From:   Stafford Horne <shorne@...il.com>
To:     Guenter Roeck <linux@...ck-us.net>
cc:     Stafford Horne <shorne@...il.com>, Jonas Bonn <jonas@...thpole.se>,
        Stefan Kristiansson <stefan.kristiansson@...nalahti.fi>,
        Andrew Morton <akpm@...ux-foundation.org>,
        linux-kernel@...r.kernel.org, openrisc@...ts.librecores.org
Subject: Re: [PATCH 5/7] openrisc: Support both old (or32) and new (or1k)
 toolchain



On Mon, 19 Sep 2016, Guenter Roeck wrote:

> On 09/18/2016 11:02 PM, Stafford Horne wrote:
>> 
>>
>>  On Sun, 18 Sep 2016, Guenter Roeck wrote:
>> 
>> >  Tested-by: Guenter Roeck <linux@...ck-us.net>
>> > 
>> >  If you plan to handle openrisc going forward, it would be great if you 
>> >  could
>> >  consider updating MAINTAINERS. The web site and git repository have been 
>> >  unreachable
>> >  for a long time.
>>
>>  Thank you,
>>  Updating maintainers was kind of on my plans, but I figured I need to
>>  prove that I kind of know what I am doing.
>> 
>
> The alternative would be to mark it as Orphaned. Which, for all practical 
> purpose,
> would be the correct state right now.

+CC The openrisc list

Understood, 
I don't think we would want that to happen.