Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From:   "D. Jeff Dionne" <djeffdionne@gmail.com>
Mime-Version: 1.0 (1.0)
Subject: Re: [PATCH 3/4] sh: remove superhyway bus support
Date:   Thu, 3 Aug 2023 16:58:38 +0900
Message-Id: <D28BDDE3-7FE6-4ACC-98B9-B6AB6D9518A3@gmail.com>
References: <20230802184849.1019466-3-arnd@kernel.org>
Cc:     John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
        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>
In-Reply-To: <20230802184849.1019466-3-arnd@kernel.org>
To:     Arnd Bergmann <arnd@kernel.org>
Precedence: bulk

On Aug 3, 2023, at 04:15, Arnd Bergmann <arnd@kernel.org> wrote:
>=20
> From: Arnd Bergmann <arnd@arndb.de>
>=20
> superhyway was only referenced on sh4-202, which is now gone, so remove it=
 all as well.
>=20
> I could find no trace of anything ever calling
> superhyway_register_driver(), not in the git history but also not on the w=
eb, so I assume this has never served any purpose on mainline kernels.

I don=E2=80=99t know, but I think it is fairly safe to assume that there wer=
e 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.

J.=