From: Rich Felker <dalias@libc.org>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Christoph Hellwig <hch@infradead.org>,
Arnd Bergmann <arnd@arndb.de>,
linux-sh@vger.kernel.org, ysato@users.sourceforge.jp,
linux-kernel@vger.kernel.org, viro@zeniv.linux.org.uk,
Rob Landley <rob@landley.net>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] sh: remove sh5 support
Date: Fri, 5 Jun 2020 11:59:54 -0400 [thread overview]
Message-ID: <20200605155954.GV1079@brightrain.aerifal.cx> (raw)
In-Reply-To: <c4900bf6-99b3-c9b9-4fd0-7f491bd46de6@physik.fu-berlin.de>
On Fri, Jun 05, 2020 at 05:47:34PM +0200, John Paul Adrian Glaubitz wrote:
> On 6/5/20 5:43 PM, Rich Felker wrote:
> >> Can you include the patch as well?
> >
> > This one is outside arch/sh and I'm not sure it's permissible to go up
> > through my tree. I was also under the impression that only part 1 was
> > needed to fix the immediate problem on sh and tha part 2 was for
> > completeness and to make sure the same doesn't happen on other archs
> > in the future, but maybe my understanding here is incorrect.
>
> Ah, sorry, I missed that. You're right, it should probably go through
> someone else's tree then.
Do you know if it's needed to un-break sh4? If so we should push to
get whoever has jurisdiction over it to include it; otherwise I'm
indifferent.
> >> And would it be okay to send a PR to Linus
> >> after that?
> >
> > Sure, will do right away once we resolve what to do with the above,
> > and provided you don't have anything else you want me to evaluate for
> > inclusion.
>
> Since we haven't agreed on the __get_user_64() patch yet, I would be
> in favor of getting the changes pulled in that have already been
> reviewed and acknowledged. I rather don't want the other contributors
> to wait any longer. Arnd in particular has done a tremendous job to
> untangle all the SH-5 code and I think we should finally get this
> in :).
Absolutely agreed.
Rich
next prev parent reply other threads:[~2020-06-05 15:59 UTC|newest]
Thread overview: 35+ 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 ` [PATCH 1/1] " Arnd Bergmann
2020-05-07 14:35 ` [GIT PULL] " Christoph Hellwig
2020-05-28 5:46 ` Christoph Hellwig
2020-05-28 5:55 ` John Paul Adrian Glaubitz
2020-05-28 9:40 ` Rob Landley
2020-05-28 16:14 ` Rich Felker
2020-05-28 22:14 ` Rich Felker
2020-05-28 22:28 ` Rob Landley
2020-05-28 22:32 ` John Paul Adrian Glaubitz
2020-05-28 22:37 ` Rich Felker
2020-05-29 14:35 ` Christoph Hellwig
2020-05-29 14:30 ` Christoph Hellwig
2020-05-29 17:53 ` Rich Felker
2020-05-29 18:22 ` Christoph Hellwig
2020-05-30 8:08 ` John Paul Adrian Glaubitz
2020-05-30 8:47 ` Geert Uytterhoeven
2020-05-31 3:20 ` Rob Landley
2020-05-31 8:03 ` John Paul Adrian Glaubitz
2020-06-01 2:55 ` Rich Felker
2020-06-01 8:16 ` John Paul Adrian Glaubitz
2020-06-01 18:13 ` Rich Felker
2020-06-01 21:12 ` Arnd Bergmann
2020-06-02 1:33 ` Rich Felker
2020-06-02 2:49 ` Andrew Morton
2020-06-02 2:53 ` Rich Felker
2020-06-03 7:27 ` 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:43 ` Rich Felker
2020-06-05 15:47 ` John Paul Adrian Glaubitz
2020-06-05 15:59 ` Rich Felker [this message]
2020-06-05 17:58 ` John Paul Adrian Glaubitz
2020-06-05 18:23 ` Geert Uytterhoeven
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=20200605155954.GV1079@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=glaubitz@physik.fu-berlin.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).