Hi Paul, On Wed, 2015-01-28 at 16:25 +0000, Paul Walmsley wrote: > Is the Kconfig checker script you mentioned on Tuesday available in the > mainline tree? I don't see anything obvious under the "Static Analysers" > section of the Makefile, but perhaps I'm overlooking it.
No, it's not. In tree you'll find scripts/checkkconfigsymbols.py. That catches over 90% of the stuff my local script catches, in less than 10% of runtime. It would certainly have caught your use of USB_ARCH_HAS_EHCI. My local script is my third (or fourth) attempt at a script that checks these kind of issues. I've used it on linux-next since for about 3/4 of a year now. While doing that I ran into people that are planning into adding similar, but far more advanced, functionality into one of the bots that is checking linux. So I never bothered making my script public. (I'm not sure what the status of those plan is now.) In the mean time I'll keep on checking linux-next with my script. That should also help to see what problems an actual bot could run into, for the benefit of those people. Problems like: - should it check each commit (I think it should only check releases); - should it be a true bot (I think it needs a wetware frontend to filter out non-issues). Hope this answers your question. Paul Bolle -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
