Re: [RFC] select and dependencies in Kconfig

Timur Tabi wrote:
> For example, if I want to add a new driver C that uses library B, I can
> just add this:
> 
> C
>     select B
> 
> If I have to use "depends on", then I would have to change the Kconfig
> option for B like this:
> 
> B
>     depends on A || C

You mean, "B... serves A, C".

However, it shouldn't matter which way around the dependencies are
written down in the Kconfigs.  What does matter is how "make
{old,menu,...}config" deal with it.
-- 
Stefan Richter
-=====-=-=== -=-= =---=
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [PATCH] missing dependencies for USB drivers in input
    • From: Al Viro <[email protected]>
  • [RFC] select and dependencies in Kconfig
    • From: Al Viro <[email protected]>
  • Re: [RFC] select and dependencies in Kconfig
    • From: Stefan Richter <[email protected]>
  • Re: [RFC] select and dependencies in Kconfig
    • From: Timur Tabi <[email protected]>

• Prev by Date: Re: [PATCH 1/2] scalable rw_mutex
• Next by Date: Re: [PATCH] powernow-k8: depend on acpi-processor for SMP systems
• Previous by thread: Re: [RFC] select and dependencies in Kconfig
• Next by thread: Re: [RFC] select and dependencies in Kconfig
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]