From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnd Bergmann Subject: Re: [PATCH 00/19] [RESEND] Remove STiH415 and STiH416 SoC platform support Date: Wed, 14 Sep 2016 15:38:58 +0200 Message-ID: <7524458.uFhxDUCqEo@wuerfel> References: <1473859677-9231-1-git-send-email-peter.griffin@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Return-path: In-Reply-To: <1473859677-9231-1-git-send-email-peter.griffin-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Peter Griffin Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, kernel-F5mvAk5X5gdBDgjK7y7TUQ@public.gmane.org, patrice.chotard-qxv4g6HH51o@public.gmane.org, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org List-Id: devicetree@vger.kernel.org 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 -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html