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: <94c3ee37-19f7-de94-9b61-bc1c06a84d72@roeck-us.net>
Date:   Mon, 19 Sep 2016 00:18:15 -0700
From:   Guenter Roeck <linux@...ck-us.net>
To:     Stafford Horne <shorne@...il.com>
Cc:     Jonas Bonn <jonas@...thpole.se>,
        Stefan Kristiansson <stefan.kristiansson@...nalahti.fi>,
        Andrew Morton <akpm@...ux-foundation.org>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 5/7] openrisc: Support both old (or32) and new (or1k)
 toolchain

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.

Guenter