> Documentation/smpl/$name_of_problem_fixed.cocci? Or maybe better > scripts/smlp/..., if you are going to add some wrapper that runs the > semantic patches on the source tree. Or something like that, a dedicated > subdirectory to store the semantic patches in individual files. The idea is to make it possible to run them, assuming the user has installed Coccinelle, so scripts seems better. > > What do you think the best way would be to introduce some check like this > > in the build environment? > > I've only heard about the tool, I haven't used it yet. Does it need to > preprocess and parse source files like sparse does, or can it check C > files without expanding macros and includes? It doesn't need to preprocess the source files. thanks, julia -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html