From: Rich Felker <dalias@libc.org>
To: 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,
Rob Landley <rob@landley.net>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [GIT PULL] sh: remove sh5 support
Date: Thu, 28 May 2020 16:14:16 +0000 [thread overview]
Message-ID: <20200528161416.GY1079@brightrain.aerifal.cx> (raw)
In-Reply-To: <20200528054600.GA29717@infradead.org>
On Wed, May 27, 2020 at 10:46:00PM -0700, Christoph Hellwig wrote:
> [adding Linus]
>
> On Thu, May 07, 2020 at 07:35:52AM -0700, Christoph Hellwig wrote:
> > Any progress on this? I plan to resend the sh dma-mapping I've been
> > trying to get upstream for a year again, and they would conflict,
> > so I could look into rebasing them first.
>
> So for years now it has been close to and in the end impossible to
> provoke sh maintainer action. At the same point hardware is pretty much
> long gone for the real commercial variants, and never took off for the
> open hardware nommu variant.
>
> Linus, would you ok with a 5.8 pull request to just kill off arch/sh/?
It is in active use. Please do not act on such a request. I would be
much quicker to ack things that actually need ack if I weren't CC'd on
hundreds of random non-arch-specific changes that don't need it, but I
understand that's how the kernel process works. If there are things
that need ack please feel free to ping.
Note that I specifically acked and requested the sh5 removal.
Rich
WARNING: multiple messages have this Message-ID (diff)
From: Rich Felker <dalias@libc.org>
To: 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,
Rob Landley <rob@landley.net>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [GIT PULL] sh: remove sh5 support
Date: Thu, 28 May 2020 12:14:16 -0400 [thread overview]
Message-ID: <20200528161416.GY1079@brightrain.aerifal.cx> (raw)
In-Reply-To: <20200528054600.GA29717@infradead.org>
On Wed, May 27, 2020 at 10:46:00PM -0700, Christoph Hellwig wrote:
> [adding Linus]
>
> On Thu, May 07, 2020 at 07:35:52AM -0700, Christoph Hellwig wrote:
> > Any progress on this? I plan to resend the sh dma-mapping I've been
> > trying to get upstream for a year again, and they would conflict,
> > so I could look into rebasing them first.
>
> So for years now it has been close to and in the end impossible to
> provoke sh maintainer action. At the same point hardware is pretty much
> long gone for the real commercial variants, and never took off for the
> open hardware nommu variant.
>
> Linus, would you ok with a 5.8 pull request to just kill off arch/sh/?
It is in active use. Please do not act on such a request. I would be
much quicker to ack things that actually need ack if I weren't CC'd on
hundreds of random non-arch-specific changes that don't need it, but I
understand that's how the kernel process works. If there are things
that need ack please feel free to ping.
Note that I specifically acked and requested the sh5 removal.
Rich
next prev parent reply other threads:[~2020-05-28 16:14 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 [this message]
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
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=20200528161416.GY1079@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=arnd@arndb.de \
--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.