From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Rob Landley <rob@landley.net>, Rich Felker <dalias@libc.org>,
Christoph Hellwig <hch@infradead.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
linux-sh@vger.kernel.org, ysato@users.sourceforge.jp,
linux-kernel@vger.kernel.org, viro@zeniv.linux.org.uk,
Geert Uytterhoeven <geert@linux-m68k.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [GIT PULL] sh: remove sh5 support
Date: Sun, 31 May 2020 08:03:13 +0000 [thread overview]
Message-ID: <eea4f39c-23d4-d435-a770-652d71268f34@physik.fu-berlin.de> (raw)
In-Reply-To: <8b4ff7fe-c10c-fc8e-72bc-88ef69bdb2b4@landley.net>
On 5/31/20 5:20 AM, Rob Landley wrote:
> On 5/30/20 3:08 AM, John Paul Adrian Glaubitz wrote:
>> On 5/29/20 7:53 PM, Rich Felker wrote:
>>> Frustratingly, I _still_ don't have an official tree on kernel.org for
>>> the purpose of being the canonical place for linux-next to pull from,
>>> due to policies around pgp keys and nobody following up on signing
>>> mine. This is all really silly since there are ridiculously many
>>> independent channels I could cryptographically validate identity
>>> through with vanishing probability that they're all compromised. For
>>> the time being I'll reactivate my repo on git.musl-libc.org.
>>
>> May I suggest to pick up these patches, for example? There might be
>> more I missed, but getting these merged should already help a lot with
>> the clean-up of arch/sh.
>
> Does that include the 2 fixes to build with current binutils I made puppy eyes
> about last -rc7 (in march)?
>
> https://marc.info/?l=linux-sh&m\x158544749818664&w=2
Yes, listed as "[PATCH 1/2] arch/sh: vmlinux.scr".
@Rich: Do you think you can merge all those fixes in your local tree within
the next days and send a PR to Linus?
Otherwise, I can volunteer to become a third maintainer for arch/sh as I have
the hardware for testing and can accept patches and send PRs.
We shouldn't let contributors to arch/sh wait for too long.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
WARNING: multiple messages have this Message-ID (diff)
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Rob Landley <rob@landley.net>, Rich Felker <dalias@libc.org>,
Christoph Hellwig <hch@infradead.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
linux-sh@vger.kernel.org, ysato@users.sourceforge.jp,
linux-kernel@vger.kernel.org, viro@zeniv.linux.org.uk,
Geert Uytterhoeven <geert@linux-m68k.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [GIT PULL] sh: remove sh5 support
Date: Sun, 31 May 2020 10:03:13 +0200 [thread overview]
Message-ID: <eea4f39c-23d4-d435-a770-652d71268f34@physik.fu-berlin.de> (raw)
In-Reply-To: <8b4ff7fe-c10c-fc8e-72bc-88ef69bdb2b4@landley.net>
On 5/31/20 5:20 AM, Rob Landley wrote:
> On 5/30/20 3:08 AM, John Paul Adrian Glaubitz wrote:
>> On 5/29/20 7:53 PM, Rich Felker wrote:
>>> Frustratingly, I _still_ don't have an official tree on kernel.org for
>>> the purpose of being the canonical place for linux-next to pull from,
>>> due to policies around pgp keys and nobody following up on signing
>>> mine. This is all really silly since there are ridiculously many
>>> independent channels I could cryptographically validate identity
>>> through with vanishing probability that they're all compromised. For
>>> the time being I'll reactivate my repo on git.musl-libc.org.
>>
>> May I suggest to pick up these patches, for example? There might be
>> more I missed, but getting these merged should already help a lot with
>> the clean-up of arch/sh.
>
> Does that include the 2 fixes to build with current binutils I made puppy eyes
> about last -rc7 (in march)?
>
> https://marc.info/?l=linux-sh&m=158544749818664&w=2
Yes, listed as "[PATCH 1/2] arch/sh: vmlinux.scr".
@Rich: Do you think you can merge all those fixes in your local tree within
the next days and send a PR to Linus?
Otherwise, I can volunteer to become a third maintainer for arch/sh as I have
the hardware for testing and can accept patches and send PRs.
We shouldn't let contributors to arch/sh wait for too long.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2020-05-31 8:03 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 22:19 [GIT PULL] sh: remove sh5 support Arnd Bergmann
2020-04-24 22:19 ` Arnd Bergmann
2020-04-24 22:19 ` [PATCH 1/1] " Arnd Bergmann
2020-04-24 22:19 ` Arnd Bergmann
2020-05-07 14:35 ` [GIT PULL] " Christoph Hellwig
2020-05-07 14:35 ` Christoph Hellwig
2020-05-28 5:46 ` Christoph Hellwig
2020-05-28 5:46 ` Christoph Hellwig
2020-05-28 5:55 ` John Paul Adrian Glaubitz
2020-05-28 5:55 ` John Paul Adrian Glaubitz
2020-05-28 9:40 ` Rob Landley
2020-05-28 9:40 ` Rob Landley
2020-05-28 16:14 ` Rich Felker
2020-05-28 16:14 ` Rich Felker
2020-05-28 22:14 ` Rich Felker
2020-05-28 22:14 ` Rich Felker
2020-05-28 22:28 ` Rob Landley
2020-05-28 22:28 ` Rob Landley
2020-05-28 22:32 ` John Paul Adrian Glaubitz
2020-05-28 22:32 ` John Paul Adrian Glaubitz
2020-05-28 22:37 ` Rich Felker
2020-05-28 22:37 ` Rich Felker
2020-05-29 14:35 ` Christoph Hellwig
2020-05-29 14:35 ` Christoph Hellwig
2020-05-29 14:30 ` Christoph Hellwig
2020-05-29 14:30 ` Christoph Hellwig
2020-05-29 17:53 ` Rich Felker
2020-05-29 17:53 ` Rich Felker
2020-05-29 18:22 ` Christoph Hellwig
2020-05-29 18:22 ` Christoph Hellwig
2020-05-30 8:08 ` John Paul Adrian Glaubitz
2020-05-30 8:08 ` John Paul Adrian Glaubitz
2020-05-30 8:47 ` Geert Uytterhoeven
2020-05-30 8:47 ` Geert Uytterhoeven
2020-05-31 3:20 ` Rob Landley
2020-05-31 3:20 ` Rob Landley
2020-05-31 8:03 ` John Paul Adrian Glaubitz [this message]
2020-05-31 8:03 ` John Paul Adrian Glaubitz
2020-06-01 2:55 ` Rich Felker
2020-06-01 2:55 ` Rich Felker
2020-06-01 8:16 ` John Paul Adrian Glaubitz
2020-06-01 8:16 ` John Paul Adrian Glaubitz
2020-06-01 18:13 ` Rich Felker
2020-06-01 18:13 ` Rich Felker
2020-06-01 21:12 ` Arnd Bergmann
2020-06-01 21:12 ` Arnd Bergmann
2020-06-02 1:33 ` Rich Felker
2020-06-02 1:33 ` Rich Felker
2020-06-02 2:49 ` Andrew Morton
2020-06-02 2:49 ` Andrew Morton
2020-06-02 2:53 ` Rich Felker
2020-06-02 2:53 ` Rich Felker
2020-06-03 7:27 ` John Paul Adrian Glaubitz
2020-06-03 7:27 ` John Paul Adrian Glaubitz
2020-06-03 7:31 ` John Paul Adrian Glaubitz
2020-06-03 7:31 ` John Paul Adrian Glaubitz
2020-06-05 15:38 ` John Paul Adrian Glaubitz
2020-06-05 15:38 ` John Paul Adrian Glaubitz
2020-06-05 15:43 ` Rich Felker
2020-06-05 15:43 ` Rich Felker
2020-06-05 15:47 ` John Paul Adrian Glaubitz
2020-06-05 15:47 ` John Paul Adrian Glaubitz
2020-06-05 15:59 ` Rich Felker
2020-06-05 15:59 ` Rich Felker
2020-06-05 17:58 ` John Paul Adrian Glaubitz
2020-06-05 17:58 ` John Paul Adrian Glaubitz
2020-06-05 18:23 ` Geert Uytterhoeven
2020-06-05 18:23 ` Geert Uytterhoeven
2020-06-06 0:50 ` Andrew Morton
2020-06-06 0:50 ` Andrew Morton
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=eea4f39c-23d4-d435-a770-652d71268f34@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=arnd@arndb.de \
--cc=dalias@libc.org \
--cc=geert@linux-m68k.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=rob@landley.net \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
--cc=ysato@users.sourceforge.jp \
/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.