On 12.1.2011 22:58, Len Brown wrote: >>> These unusable config combinations should be prevented via Kconfig. >>> That prevents users from selecting them, which otherwise adds to >>> our workload and to theirs. It also prevents false-positives >>> during our useful randconfig testing. >> >> But it is kind of difficult to achieve IMhO. For example, there are options >> that are only SELECTed if something else is set, but randconfig doesn't seem >> to care. > > Kconfig select needs to be fixed so that it is not possible to > select something if that something's dependencies are not met. Right now, it issues a warning in such case. I think changing it to a fatal error would be too premature, not long ago there were a couple of annoying false positives. But from the rest of the thread, I conclude that you actually meant "not possible to select something if that something's dependencies CANNOT be met", i.e. automatically select dependencies if that is possible. That was actually one of the goals of Vegard Nossum's GSoC poject last year, but I haven't heard of any outcome yet. Vegard, is there something we could use, be it code or mistakes we could learn from? Thanks, Michal -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
