mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: "D. Jeff Dionne" <djeffdionne@gmail.com>,
	Arnd Bergmann <arnd@kernel.org>
Cc: linux-sh@vger.kernel.org, Rich Felker <dalias@libc.org>,
	Yoshinori Sato <ysato@users.sourceforge.jp>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH 3/4] sh: remove superhyway bus support
Date: Thu, 03 Aug 2023 10:44:33 +0200	[thread overview]
Message-ID: <fecb873aefad8dd4c1d89935cf8f7790e9ba231d.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <D28BDDE3-7FE6-4ACC-98B9-B6AB6D9518A3@gmail.com>

Hi Jeff!

On Thu, 2023-08-03 at 16:58 +0900, D. Jeff Dionne wrote:
> On Aug 3, 2023, at 04:15, Arnd Bergmann <arnd@kernel.org> wrote:
> > 
> > From: Arnd Bergmann <arnd@arndb.de>
> > 
> > superhyway was only referenced on sh4-202, which is now gone, so remove it all as well.
> > 
> > I could find no trace of anything ever calling
> > superhyway_register_driver(), not in the git history but also not on the web, so I assume this has never served any purpose on mainline kernels.
> 
> I don’t know, but I think it is fairly safe to assume that there were no superhyway implementations other than internal to SuperH Co (or Hitachi).  Probably not at ST either.
> 
> I think this board, and infrastructure, can go without affecting any actual (even historical) user.  If anyone wants further conformation that there are/were no users of this in the wild, raise a flag and I will find out.

OK, I'll think about applying this series. The thing is, we're going to convert SuperH
to device trees anyways. We're waiting now Yoshinori to post a rebased version of the
patch series.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

  reply	other threads:[~2023-08-03  8:44 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-02 18:48 [PATCH 1/4] sh: remove stale microdev board Arnd Bergmann
2023-08-02 18:48 ` [PATCH 2/4] sh: remove unused sh4-202 support Arnd Bergmann
2023-09-08 10:00   ` John Paul Adrian Glaubitz
2023-08-02 18:48 ` [PATCH 3/4] sh: remove superhyway bus support Arnd Bergmann
2023-08-03  7:58   ` D. Jeff Dionne
2023-08-03  8:44     ` John Paul Adrian Glaubitz [this message]
2023-08-03  9:19       ` Arnd Bergmann
2023-08-03  9:36         ` John Paul Adrian Glaubitz
2023-08-03  9:58           ` Arnd Bergmann
2023-09-08 10:02   ` John Paul Adrian Glaubitz
2023-08-02 18:48 ` [PATCH 4/4] sh: machvec: remove custom ioport_{un,}map() Arnd Bergmann
2023-09-08 10:10   ` John Paul Adrian Glaubitz
2023-09-08 10:20     ` Geert Uytterhoeven
2023-09-08 10:21       ` John Paul Adrian Glaubitz
2023-09-08 10:23   ` John Paul Adrian Glaubitz
2023-09-13 12:32   ` Geert Uytterhoeven
2023-09-13 14:08     ` Arnd Bergmann
2023-09-13 14:13       ` Geert Uytterhoeven
2023-09-13 14:30         ` Arnd Bergmann
2023-09-14  6:23           ` John Paul Adrian Glaubitz
2023-09-14 15:56             ` Arnd Bergmann
2023-09-15 15:41           ` Geert Uytterhoeven
2023-09-15 15:49             ` Arnd Bergmann
2023-09-21  7:45               ` John Paul Adrian Glaubitz
2023-09-21  8:52                 ` Geert Uytterhoeven
2023-09-25  7:08                   ` Yoshinori Sato
2023-09-25  7:36                     ` Arnd Bergmann
2023-09-26 22:15                     ` John Paul Adrian Glaubitz
2023-09-08  9:59 ` [PATCH 1/4] sh: remove stale microdev board John Paul Adrian Glaubitz
2023-09-09 22:06 ` John Paul Adrian Glaubitz

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=fecb873aefad8dd4c1d89935cf8f7790e9ba231d.camel@physik.fu-berlin.de \
    --to=glaubitz@physik.fu-berlin.de \
    --cc=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=dalias@libc.org \
    --cc=djeffdionne@gmail.com \
    --cc=geert+renesas@glider.be \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.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

all inboxes | Powered by JetHome®