lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <D28BDDE3-7FE6-4ACC-98B9-B6AB6D9518A3@gmail.com>
Date:   Thu, 3 Aug 2023 16:58:38 +0900
From:   "D. Jeff Dionne" <djeffdionne@...il.com>
To:     Arnd Bergmann <arnd@...nel.org>
Cc:     John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>,
        linux-sh@...r.kernel.org, Rich Felker <dalias@...c.org>,
        Yoshinori Sato <ysato@...rs.sourceforge.jp>,
        Geert Uytterhoeven <geert+renesas@...der.be>,
        linux-kernel@...r.kernel.org, Arnd Bergmann <arnd@...db.de>
Subject: Re: [PATCH 3/4] sh: remove superhyway bus support

On Aug 3, 2023, at 04:15, Arnd Bergmann <arnd@...nel.org> wrote:
> 
> From: Arnd Bergmann <arnd@...db.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.

J.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ