From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Corentin Chary <corentin.chary@gmail.com>,
sedat.dilek@gmail.com, Matthew Garrett <mjg@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
platform-driver-x86@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
Randy Dunlap <randy.dunlap@oracle.com>
Subject: Re: linux-next: Tree for December 8 (drivers/platform/x86/Kconfig:422:error: recursive dependency detected!)
Date: Wed, 8 Dec 2010 09:46:04 -0800 [thread overview]
Message-ID: <20101208174603.GA7107@core.coreip.homeip.net> (raw)
In-Reply-To: <1291801990.5992.105.camel@i7.infradead.org>
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.
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.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2010-12-08 17:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-08 8:17 Sedat Dilek
2010-12-08 9:12 ` Corentin Chary
2010-12-08 9:18 ` Sedat Dilek
2010-12-08 9:20 ` Berg, Johannes
2010-12-08 9:28 ` Sedat Dilek
2010-12-08 9:51 ` Sedat Dilek
2010-12-08 9:53 ` David Woodhouse
2010-12-08 10:12 ` Sedat Dilek
2010-12-08 17:46 ` Dmitry Torokhov [this message]
2010-12-08 21:51 ` Randy Dunlap
2010-12-08 22:12 ` Dmitry Torokhov
2010-12-08 22:37 ` Thadeu Lima de Souza Cascardo
2010-12-08 23:08 ` David Woodhouse
2010-12-08 23:31 ` Dmitry Torokhov
2010-12-08 23:35 ` David Woodhouse
2010-12-08 23:49 ` Dmitry Torokhov
2010-12-08 23:58 ` Randy Dunlap
2010-12-08 23:34 ` Randy Dunlap
2010-12-08 23:41 ` David Woodhouse
2010-12-08 23:52 ` Dmitry Torokhov
2010-12-08 17:31 ` Randy Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101208174603.GA7107@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=corentin.chary@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg@redhat.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sedat.dilek@gmail.com \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®