On Wed, May 12, 2010 at 02:42:30PM +0800, Américo Wang wrote: > On Mon, May 10, 2010 at 06:24:24PM +0200, Nicolas Palix wrote: > >Four targets are added. Each one generates a different > >output kind: context, patch, org, report. > >Every SmPL file in 'scripts/coccinelle' is given to the spatch frontend > >(located in the 'scripts' directory), and applied to the entire > >source tree. > > > >Signed-off-by: Nicolas Palix <npalix@xxxxxxx> > >Signed-off-by: Julia Lawall <julia@xxxxxxx> > > This is great! Totally agreed. > I would like to see coccinelle to be integrated with kbuild, but the > name 'coccicheck' is really confusing, how about 'sema_check'? Which > means 'semantic check'. I think its okay to keep coccicheck because its the name of the tool called. We do the same with 'make cscope'. But since I am a bit lazy I would prefer a shorter name, probably just 'make cocci'? > Or we can use something like for sparse, i.e. 'make C=1' etc.. Yes, this would also make sense. As a developer I could add this and only the code I changed is checked. Joerg -- To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
