Messages in this thread | | | Date | Sun, 20 May 2007 12:17:17 +0200 | From | Sam Ravnborg <> | Subject | Re: RFC: kconfig select warnings bogus? |
| |
On Sun, May 20, 2007 at 10:40:33AM +0100, Russell King wrote: > > Do we really need an exhaustive set of configuration combinations to > run through Kconfig to find possible missing symbols? Or do we need a > Kconfig lint to find them? > > If we're going to make Kconfig warn on missing symbols only when they're > attempted to be selected, you'll have to choose one of those two options. > Choosing none is not an option. The best solution would be to give kconfig full knowledge of all Kconfig files. Then the "undefined symbol" is no longer a warning but an error.
That would require a bit of kconfig surgery that we should do one day. But giving kconfig full knowledge would gain a lot in several scenarios. Turning the undefined symbol to an error is just one part of it.
Sam - 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/
| |