Searched refs:SPFLAGS (Results 1 – 3 of 3) sorted by relevance
34 # You can use SPFLAGS to append extra arguments to coccicheck or override any38 # A good example for use of SPFLAGS is if you want to debug your cocci script,42 # $ make coccicheck MODE=report DEBUG_FILE="all.err" SPFLAGS="--profile --show-trying" M=./drivers/mfd/arizona-irq.c50 echo $SPFLAGS | grep -E -e "--profile|--show-trying" 2>&1 > /dev/null101 # You can override by using SPFLAGS188 # You can override heuristics with SPFLAGS, these must always go last189 OPTIONS="$OPTIONS $SPFLAGS"
221 You can use SPFLAGS to add debugging flags; for instance you may want to222 add both ``--profile --show-trying`` to SPFLAGS when debugging. For example227 … make coccicheck DEBUG_FILE="err.log" MODE=report SPFLAGS="--profile --show-trying" M=./drivers/mfd267 override any of the kernel's .coccicheck's settings using SPFLAGS.280 You can override with your own preferred index option by using SPFLAGS. Take284 carries its own .cocciconfig, you will need to use SPFLAGS to use idutils if291 Additional flags can be passed to spatch through the SPFLAGS295 make SPFLAGS=--use-glimpse coccicheck307 make SPFLAGS=--use-idutils coccicheck312 make SPFLAGS="--use-idutils /full-path/to/ID" coccicheck
11 virtual explain // explain decisions in the patch (SPFLAGS="-D explain")