linux-kernel - Re: [PATCH 00/19] [RESEND] Remove STiH415 and STiH416 SoC platform support

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]

Date:   Wed, 14 Sep 2016 15:38:58 +0200
From:   Arnd Bergmann <arnd@...db.de>
To:     Peter Griffin <peter.griffin@...aro.org>
Cc:     linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
        kernel@...inux.com, patrice.chotard@...com,
        devicetree@...r.kernel.org, lee.jones@...aro.org
Subject: Re: [PATCH 00/19] [RESEND] Remove STiH415 and STiH416 SoC platform support

On Wednesday, September 14, 2016 2:27:38 PM CEST Peter Griffin wrote:
> Resending due to incorrect Cc tags.
> 
> ST have sent patches which remove clock support for these SoCs [1]
> which once applied mean the platform will no longer boot.
> 
> This series cleans up various STi platform drivers which have
> support for these SoC's, by removing code, and updating the DT
> documentation accordingly. Some drivers such as miphy365 and
> stih41x-usb can be removed completely because the IP is only
> found on these legacy SoC's.
> 
> Once this series is applied, drm display driver, and ALSA SoC
> are the main two remaining references to the legacy SoCs, other
> than clocks which already have patches on the ML.

It would be good to have a better explanation that "it's already
broken by some other commit". Is this a platform that never shipped
to end-users, or is it possible that someone out there actually
has a machine with one of these SoCs?

	Arnd