From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.linuxfoundation.org ([140.211.169.12]:35528 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S941491AbcJaMVc (ORCPT ); Mon, 31 Oct 2016 08:21:32 -0400 Date: Mon, 31 Oct 2016 06:21:40 -0600 From: Greg Kroah-Hartman To: Geert Uytterhoeven Cc: Laura Abbott , Rob Herring , Arnd Bergmann , "linux-kernel@vger.kernel.org" , linux-clk Subject: Re: [PATCH] driver core: Make Kconfig text for DEBUG_TEST_DRIVER_REMOVE stronger Message-ID: <20161031122140.GB6774@kroah.com> References: <120f00f2-94b6-aead-7bb4-9917bc338660@redhat.com> <1475856570-10743-1-git-send-email-labbott@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: Sender: linux-clk-owner@vger.kernel.org List-ID: On Mon, Oct 31, 2016 at 11:12:45AM +0100, Geert Uytterhoeven wrote: > On Fri, Oct 7, 2016 at 6:09 PM, Laura Abbott wrote: > > The current state of driver removal is not great. > > CONFIG_DEBUG_TEST_DRIVER_REMOVE finds lots of errors. The help text > > currently undersells exactly how many errors this option will find. Add > > a bit more description to indicate this option shouldn't be turned on > > unless you actually want to debug driver removal. The text can be > > changed later when more drivers are fixed up. > > Indeed, this is failing miserably for e.g. SoC clock drivers using > platform_driver_probe(), which are never retried, rendering the complete > system useless. Why are they never retried?