From mboxrd@z Thu Jan 1 00:00:00 1970 From: Randy Dunlap Subject: Re: linux-next: Tree for December 8 (drivers/platform/x86/Kconfig:422:error: recursive dependency detected!) Date: Wed, 8 Dec 2010 13:51:05 -0800 Message-ID: <20101208135105.a8482d46.randy.dunlap@oracle.com> References: <1291801990.5992.105.camel@i7.infradead.org> <20101208174603.GA7107@core.coreip.homeip.net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: Received: from rcsinet10.oracle.com ([148.87.113.121]:45035 "EHLO rcsinet10.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754003Ab0LHVwm (ORCPT ); Wed, 8 Dec 2010 16:52:42 -0500 In-Reply-To: <20101208174603.GA7107@core.coreip.homeip.net> Sender: platform-driver-x86-owner@vger.kernel.org List-ID: To: Dmitry Torokhov Cc: David Woodhouse , Corentin Chary , sedat.dilek@gmail.com, Matthew Garrett , LKML , platform-driver-x86@vger.kernel.org, Stephen Rothwell On Wed, 8 Dec 2010 09:46:04 -0800 Dmitry Torokhov wrote: > On Wed, Dec 08, 2010 at 09:53:09AM +0000, David Woodhouse wrote: > > On Wed, 2010-12-08 at 10:12 +0100, Corentin Chary wrote: > > > > > > I don't really see how it's a recursive dependency, but maybe it's > > > time to clean this KConfig. > > > What is our current policy about that ? > > > > > > I think we should *depends* on important subsystem (ACPI, INPUT, ...) > > > and select obscure things so > > > that the driver does not get lost if you don't enable the leds. > > > > A better policy is: "NEVER USE SELECT". > > > > No, this is BS. User selecting, for example, a button driver should not > care that it is working in polling mode only and needs polled device > library to work. As it was said before, drivers need to depend on major > subsystems and select minors and library modules. I dislike select, but reality is that modules do need to select/enable library code and minor features sometimes. OTOH, where drivers/platform/x86/Kconfig:ACPI_CMPC does "select INPUT" to enable an entire subsystem is wrong and bad IMO. > The fact that our Kconfig can't really provide us with the functionality > we desire (be it because the logic is fuzzy and hard to formalize or > some other reason) shoud not force "NO SELECT" policy, we just need to > be careful when using it. --- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code ***