All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Stafford Horne <shorne@gmail.com>
Cc: Jonas Bonn <jonas@southpole.se>,
	Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, openrisc@lists.librecores.org
Subject: Re: [PATCH 5/7] openrisc: Support both old (or32) and new (or1k) toolchain
Date: Mon, 19 Sep 2016 07:39:53 -0700	[thread overview]
Message-ID: <436317ac-6898-d9c2-36eb-79a0b3dc333a@roeck-us.net> (raw)
In-Reply-To: <alpine.LFD.2.20.1609192247170.2352@lianli.shorne-pla.net>

On 09/19/2016 07:04 AM, Stafford Horne wrote:
>
>
> 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@roeck-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@southpole.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?
>

Nope, that won't work. Linus will not accept pull requests without signed key,
or at least I would be very surprised if he does. You'll have to get your key
signed. I understand that may be tricky, with you being in Japan (if that is
you ;-), but we can't help it.

Guenter

> -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@southpole.se>
> -W:    http://openrisc.net
> +M:    Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>
> +M:    Stafford Horne <shorne@gmail.com>
> +W:    http://openrisc.io
> +L:    openrisc@lists.librecores.org
> +T:    https://github.com/openrisc/linux.git
>  S:    Maintained
> -T:    git git://openrisc.net/~jonas/linux
>  F:    arch/openrisc/
>
>  OPENVSWITCH
>
> --
>

WARNING: multiple messages have this Message-ID (diff)
From: Guenter Roeck <linux@roeck-us.net>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [PATCH 5/7] openrisc: Support both old (or32) and new (or1k) toolchain
Date: Mon, 19 Sep 2016 07:39:53 -0700	[thread overview]
Message-ID: <436317ac-6898-d9c2-36eb-79a0b3dc333a@roeck-us.net> (raw)
In-Reply-To: <alpine.LFD.2.20.1609192247170.2352@lianli.shorne-pla.net>

On 09/19/2016 07:04 AM, Stafford Horne wrote:
>
>
> 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@roeck-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@southpole.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?
>

Nope, that won't work. Linus will not accept pull requests without signed key,
or at least I would be very surprised if he does. You'll have to get your key
signed. I understand that may be tricky, with you being in Japan (if that is
you ;-), but we can't help it.

Guenter

> -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@southpole.se>
> -W:    http://openrisc.net
> +M:    Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>
> +M:    Stafford Horne <shorne@gmail.com>
> +W:    http://openrisc.io
> +L:    openrisc at lists.librecores.org
> +T:    https://github.com/openrisc/linux.git
>  S:    Maintained
> -T:    git git://openrisc.net/~jonas/linux
>  F:    arch/openrisc/
>
>  OPENVSWITCH
>
> --
>



  parent reply	other threads:[~2016-09-19 14:39 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-16 14:42 [PATCH 0/7] openrisc: Misc fixes from backlog Stafford Horne
2016-09-16 14:42 ` [PATCH 1/7] Apply transparent_union attribute to union semun Stafford Horne
2016-09-16 15:57   ` kbuild test robot
2016-09-16 23:37   ` kbuild test robot
2016-09-17  0:06     ` Stafford Horne
2016-09-17  0:06       ` [OpenRISC] " Stafford Horne
2016-09-19 14:26   ` Jonas Bonn
2016-09-19 14:47     ` Stafford Horne
2016-09-16 14:43 ` [PATCH 2/7] openrisc: fix PTRS_PER_PGD define Stafford Horne
2016-09-19 14:27   ` Jonas Bonn
2016-09-16 14:43 ` [PATCH 3/7] openrisc: restore call-saved regs on sigreturn Stafford Horne
2016-09-19 14:28   ` Jonas Bonn
2016-09-19 14:50     ` Stafford Horne
2016-09-27 13:54       ` Stafford Horne
2016-09-16 14:43 ` [PATCH 4/7] openrisc: Add thread-local storage (TLS) support Stafford Horne
2016-09-19 14:25   ` Jonas Bonn
2016-09-19 14:43     ` Stafford Horne
2016-09-16 14:43 ` [PATCH 5/7] openrisc: Support both old (or32) and new (or1k) toolchain Stafford Horne
2016-09-18 15:26   ` Guenter Roeck
2016-09-19  6:02     ` Stafford Horne
2016-09-19  7:18       ` Guenter Roeck
2016-09-19  9:11         ` Stafford Horne
2016-09-19  9:11           ` [OpenRISC] " Stafford Horne
2016-09-19 13:17           ` Guenter Roeck
2016-09-19 13:17             ` [OpenRISC] " Guenter Roeck
2016-09-19 14:04             ` Stafford Horne
2016-09-19 14:04               ` [OpenRISC] " Stafford Horne
2016-09-19 14:35               ` Jonas Bonn
2016-09-19 14:35                 ` [OpenRISC] " Jonas Bonn
2016-09-19 14:55                 ` Guenter Roeck
2016-09-19 14:55                   ` [OpenRISC] " Guenter Roeck
2016-09-19 14:58                 ` Stefan Wallentowitz
2016-09-19 15:36                   ` Jeremy Bennett
2016-09-19 16:09                     ` Stafford Horne
2016-09-19 16:27                       ` Jeremy Bennett
2016-09-19 17:15                         ` Stefan Wallentowitz
2016-09-19 17:49                           ` Jeremy Bennett
2016-09-19 14:59                 ` Stefan Wallentowitz
2016-09-19 15:16                 ` Stafford Horne
2016-09-19 15:16                   ` [OpenRISC] " Stafford Horne
2016-09-19 14:39               ` Guenter Roeck [this message]
2016-09-19 14:39                 ` Guenter Roeck
2016-09-20 10:01                 ` Stafford Horne
2016-09-20 10:01                   ` [OpenRISC] " Stafford Horne
2016-09-16 14:43 ` [PATCH 6/7] openrisc: add SMP and NR_CPUS Kconfig options Stafford Horne
2016-09-19 14:31   ` Jonas Bonn
2016-09-19 14:54     ` Stafford Horne
2016-09-16 14:43 ` [PATCH 7/7] openrisc: remove the redundant of_platform_populate Stafford Horne
2016-09-19 14:32   ` Jonas Bonn
2016-09-19 14:58     ` Stafford Horne
2016-09-19 16:14     ` Rob Herring
2016-09-16 14:51 ` [PATCH 0/7] openrisc: Misc fixes from backlog Stafford Horne
2016-09-16 14:51   ` [OpenRISC] " Stafford Horne

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=436317ac-6898-d9c2-36eb-79a0b3dc333a@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=akpm@linux-foundation.org \
    --cc=jonas@southpole.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openrisc@lists.librecores.org \
    --cc=shorne@gmail.com \
    --cc=stefan.kristiansson@saunalahti.fi \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.