From: Adrian Bunk <bunk@kernel.org>
To: David Miller <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kconfig 'depend' vs. 'select'
Date: Mon, 28 Apr 2008 09:39:54 +0300 [thread overview]
Message-ID: <20080428063953.GA2088@cs181133002.pp.htv.fi> (raw)
In-Reply-To: <20080427.174536.62560212.davem@davemloft.net>
On Sun, Apr 27, 2008 at 05:45:36PM -0700, David Miller wrote:
>
> I'm trying to stir up interest in solving a problem that seems to pop
> up frequently. :)
>
> The short story is:
>
> 1) If you say your driver "depend"s on a subsystem providing a set of
> interfaces you need, this doesn't work properly if your driver is
> marked built-in and that subsystem you need is modular for some
> reason.
>...
This should work.
Can you give an example of the problem you are thinking of?
> So if you had, for example:
>
> config FOO_API
> ...
>
> and then you had two drivers:
>
> config DRIVER1
> tristate ...
> needs FOO_API
>
> config DRIVER2
> tristate ...
> needs FOO_API
>
> and DRIVER1 was built modular but DRIVER2 was built-in,
> the Kconfig system would make sure FOO_API were built-in.
>
> The "needs" name and syntax is just something arbitrary I came up
> with, don't take it too seriously :-)
What about "select"?
That's exactly what it's doing.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2008-04-28 6:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-28 0:45 David Miller
2008-04-28 4:58 ` Arjan van de Ven
2008-04-28 6:32 ` Seewer Philippe
2008-04-28 6:40 ` David Miller
2008-04-28 6:39 ` Adrian Bunk [this message]
2008-04-28 6:42 ` David Miller
2008-04-28 8:13 ` Adrian Bunk
2008-04-28 8:54 ` David Miller
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=20080428063953.GA2088@cs181133002.pp.htv.fi \
--to=bunk@kernel.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
/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®