On 22 March 2018 at 17:30, Eric Blake <ebl...@redhat.com> wrote: > I'm less certain of whether our Coccinelle scripts have easy ways to exclude > specific files. We already have scripts/cocci-macro-file.h to help > Coccinelle not choke on some our existing files, but I'm not sure if > Coccinelle has a config-file like way that is easy to maintain as a data > file in-tree for blacklist files to leave alone (right now, when I run > Coccinelle, I have to manually remember to pass a long command line cribbed > out of the commit message of an earlier run to pick up things like > cocci-macro-file.h, instead of an easy formula that points to a single > config file to pull in all the usual options).
Coccinelle itself doesn't seem to have a config file mechanism. We could probably approximate one by using a wrapper script that skips some files and run the passed spatch file on the rest; scripts/clean-includes has some "skip files we don't want to try to run on" code that could perhaps be generalized. thanks -- PMM
