On Fri, Sep 26, 2014 at 2:34 PM, Matt Fleming <matt@xxxxxxxxxxxxxxxxx> wrote: > On Fri, 26 Sep, at 01:59:15PM, Paul Bolle wrote: >> >> I have a 800 line perl monster that checks for stuff like this. It's not >> very sophisticated but smart enough to spot typos like this one. I try >> to have it check each linux-next (and mainline) release. > > Very cool. > >> (I think Valentin Rothberg is trying to automate this properly. See >> http://www.linuxplumbersconf.org/2014/ocw/sessions/1863 .) > > Have either of you guys thought about asking for this to be included > with the 0-day kbuild bot or submitted under scripts/? > > It certainly seems like a useful bit of functionality. Yes, I was talking with Greg about including the tool in the 0-day testing. In addition, I am working on a patch to change the scripts/checkkconfigsymbols script (https://lkml.org/lkml/2014/9/22/336). The mayor difference between my tool and the script is that the script can only find bugs on a symbolic level (i.e., a reference on an feature that is not defined in Kconfig). The tool that I will present at the Plumbers Conference is additionally able to detect issue on the logic level, for instance an #ifdef block that can never be compiled as its precondition is contradictory. I will send some patches the next weeks to show which bugs can be detected with the tool. > Fengguang, the interesting bits of this thread start here, > > https://lkml.kernel.org/r/1411730854.7866.10.camel@x220 > > -- > Matt Fleming, Intel Open Source Technology Center -- To unsubscribe from this list: send the line "unsubscribe linux-efi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
