linux-kernel - Re: [PATCH 1/1] OpenRISC: Fix kernel build problem on OpenRISC

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] [day] [month] [year] [list]

Message-ID: <5579AC71.1030607@roeck-us.net>
Date:	Thu, 11 Jun 2015 08:42:41 -0700
From:	Guenter Roeck <linux@...ck-us.net>
To:	Paul Bolle <pebolle@...cali.nl>
CC:	Jonas Bonn <jonas@...thpole.se>, anees <rean12is@...il.com>,
	linux-kernel@...r.kernel.org,
	Stefan Kristiansson <stefan.kristiansson@...nalahti.fi>
Subject: Re: [PATCH 1/1] OpenRISC: Fix kernel build problem on OpenRISC

On 06/11/2015 02:52 AM, Paul Bolle wrote:
> On Wed, 2015-06-10 at 13:21 -0700, Guenter Roeck wrote:
>> Wonder if I should step in as interim maintainer to handle urgent
>> requests like this one. Comments, thoughts, anyone ?
>
> This is about a pretty major build issue, that's been known for ten
> months now, isn't? If that's correct, this is not an urgent request, but
> a chronic issue. So in that case anyone who cares about OpenRISC should
> consider taking over. Because this looks like an orphaned architecture
> to me.
>

Those using the architecture simply apply the patch, or a similar patch,
or use the tree Stefan maintains at github.

Sure, we can wait until Stefan gets a public key and we can add him
as maintainer. I guess the active users use Stefan's tree at github
anyway.

Guenter

--
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/