On Wed, Apr 06, 2011 at 08:12:22PM +0200, Paul Bolle wrote: > On Wed, 2011-04-06 at 16:21 +0200, Johannes Berg wrote: > > On Wed, 2011-04-06 at 23:11 +0900, Mark Brown wrote: > > > On Wed, Apr 06, 2011 at 11:21:19AM +0200, Antonio Ospite wrote: > > > > > > > + tristate "Generic rfkill regulator driver" > > > > + depends on RFKILL || !RFKILL > > > > > > That looks *odd*. > > > > That's normal for rfkill -- if RFKILL==n then this can be anything since > > the rfkill API goes all no-op inlines, but if RFKILL==m then this can't > > be ==y. "depends on !RFKILL" covers the former, "depends on RFKILL" the > > latter. > > But doesn't > depends on RFKILL || !RFKILL > > always evaluate to true when running "make *config"? (Even if RFKILL is > an unknown symbol when that expression is parsed!) > > I'd say that dependencies such as this one might as well be dropped from > their Kconfig file. The syntax may seem strange, but basically it just says "don't let me by y if RFKILL is m". -- John W. Linville Someday the world will need a hero, and you linville@xxxxxxxxxxxxx might be all we have. Be ready. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
