![]() | ||||||||||
Messages in this thread |
On Monday 2008-03-24 05:05, Henrique de Moraes Holschuh wrote: > > In your menuconfig patch series to convert menu into menuconfig, > you used "if <new menuconfig symbol" quite often. > > That causes serious issues with "select". E.g. currently "select > LEDS_CLASS" does not work, because it is inside a "if NEW_LEDS". >[...] > What's the best solution for this? Drop the "if <menuconfig symbol>" > and add lots of "depends on <menuconfig symbol>"? Or hunt down every > symbol selected inside an if and add the required select for the > menuconfig symbol? It "does not work" either if LEDS_CLASS is put outside of the if block and instead gets a "depends on LEDS_CLASS". So I am not sure what the problem you perceive really is, other than "enabling A selecting B depending on (turned off) C"-is-allowed. :) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | |||||||||
| Last update: 2008-03-24 05:51 [from the cache] ©2003-2008 | ||||||||||