From: Rich Felker <dalias@libc.org>
To: Rob Landley <rob@landley.net>
Cc: Matthew Wilcox <willy@infradead.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Linux-sh list <linux-sh@vger.kernel.org>,
Linux-Arch <linux-arch@vger.kernel.org>
Subject: Re: [PATCH] sh: remove unneeded constructor.
Date: Sun, 5 Aug 2018 12:32:34 -0400 [thread overview]
Message-ID: <20180805163234.GR1392@brightrain.aerifal.cx> (raw)
In-Reply-To: <4e9e1599-9dbf-75dc-561e-77d5cb063714@landley.net>
On Sun, Aug 05, 2018 at 10:54:56AM -0500, Rob Landley wrote:
> On 08/04/2018 05:51 AM, Matthew Wilcox wrote:
> > On Sat, Aug 04, 2018 at 12:47:08PM +0200, Geert Uytterhoeven wrote:
> >> You do want to readd the __GFP_ZERO flag to the second user of PGALLOC_GFP,
> >> don't you?
> >
> > I missed that! Probably only relevant for SH-64. But yes ... probably better
> > to make this explicit then:
>
> As far as I know sh5/sh-64 never shipped, it was just some prototype hardware
> that didn't go to production?
I'm not sure about the details, but GCC has removed support and it's
effectively dead. I would be happy to merge patches removing the
existing SH-64 stuff in the kernel too. I'm not sure if generality to
support LP64 should be left in the arch/sh tree for future or if the
eventual 64-bit j-core should just be done as a separate arch tree; I
suspect the latter might be cleaner.
Rich
next prev parent reply other threads:[~2018-08-05 18:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180731051519.101249-1-ysato@users.sourceforge.jp>
2018-08-01 7:42 ` [PATCH] sh: remove unneeded constructor Geert Uytterhoeven
2018-08-01 11:13 ` Yoshinori Sato
2018-08-04 10:35 ` Matthew Wilcox
2018-08-04 10:47 ` Geert Uytterhoeven
2018-08-04 10:51 ` Matthew Wilcox
2018-08-05 15:54 ` Rob Landley
2018-08-05 16:32 ` Rich Felker [this message]
2018-08-05 22:48 ` Rob Landley
2018-08-05 23:33 ` Rich Felker
2018-08-06 6:57 ` Geert Uytterhoeven
2018-08-06 8:53 ` Arnd Bergmann
2018-08-10 18:18 ` Rob Landley
2020-06-06 16:32 ` Rich Felker
2020-06-06 16:32 ` Rich Felker
2020-06-08 13:01 ` Matthew Wilcox
2020-06-08 13:01 ` Matthew Wilcox
2018-08-01 11:20 ` Matthew Wilcox
2018-08-01 23:02 ` Rich Felker
2018-08-02 2:47 ` Matthew Wilcox
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=20180805163234.GR1392@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=geert@linux-m68k.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=rob@landley.net \
--cc=willy@infradead.org \
--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).