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.1609192247170.2352@lianli.shorne-pla.net>
Date:   Mon, 19 Sep 2016 23:04:10 +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/19/2016 02:11 AM, Stafford Horne wrote:
>> 
>>
>>  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.
>> 
> Look at the entry today:
>
> OPENRISC ARCHITECTURE
> M:      Jonas Bonn <jonas@...thpole.se>
> W:      http://openrisc.net
> S:      Maintained
> T:      git git://openrisc.net/~jonas/linux
> F:      arch/openrisc/
>
> At the very least, W: and T: are incorrect and need to be updated or removed.
> Plus, apparently there is a L:, and "T: https://github.com/openrisc/linux"
> might be appropriate.
>

Thanks,
I am aware of this, we have since setup a new website, mailing list and as 
you have found, git repo. Stefan has been nominated as the maintainer by 
Jonas on a previous mail thread.

The issue (as we see it) is that neither Stefan or I have signed PGP keys 
by anyone in the web of trust.

I sent this patch set with a cover lett trying to explain of the 
situation trying to get some help.  Your reponses are very helpful.

Do you think I should just send "git pull" reuqests to Linus with a self 
signed pgp key and eplaination to see how it goes?

-Stafford

FYI
I have a change as following in my backlog, as follows:

---
@@ -8691,10 +8063,12 @@ F:      drivers/of/overlay.c
  F:     drivers/of/resolver.c

  OPENRISC ARCHITECTURE
-M:	Jonas Bonn <jonas@...thpole.se>
-W:	http://openrisc.net
+M:	Stefan Kristiansson <stefan.kristiansson@...nalahti.fi>
+M:	Stafford Horne <shorne@...il.com>
+W:	http://openrisc.io
+L:	openrisc@...ts.librecores.org
+T:	https://github.com/openrisc/linux.git
  S:	Maintained
-T:	git git://openrisc.net/~jonas/linux
  F:	arch/openrisc/

  OPENVSWITCH

--