On 01/12/11 13: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. s/randconfig/kconfig/ > Kconfig select needs to be fixed so that it is not possible to > select something if that something's dependencies are not met. > > This long standing issue is independent of randconfig, > but Randy can probably attest that a measurable portion > of the randconfig failures are due to this bug. Certainly. At least now we have a kconfig warning on this class of problem. -- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code *** -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
