Message ID | patch-v4-4.6-48810f7390c-20220705T134033Z-avarab@gmail.com (mailing list archive) |
---|---|
State | Accepted |
Commit | 7a9a10b10e2f14ffb7c17e59f147186f85a2a94e |
Headers | show |
Series | add and apply a rule to find "unused" init+free | expand |
diff --git a/Makefile b/Makefile index c4064f8394f..669828a2a6b 100644 --- a/Makefile +++ b/Makefile @@ -3161,9 +3161,11 @@ $(COCCI_TEST_RES_GEN): .build/contrib/coccinelle/tests/%.res : contrib/coccinell .PHONY: coccicheck-test coccicheck-test: $(COCCI_TEST_RES_GEN) +coccicheck: coccicheck-test coccicheck: $(addsuffix .patch,$(filter-out %.pending.cocci,$(wildcard contrib/coccinelle/*.cocci))) # See contrib/coccinelle/README +coccicheck-pending: coccicheck-test coccicheck-pending: $(addsuffix .patch,$(wildcard contrib/coccinelle/*.pending.cocci)) .PHONY: coccicheck coccicheck-pending
Have the newly introduced "coccicheck-test" target run implicitly when "coccicheck" itself is run. As with e.g. the "check-chainlint" target (see [1]) it makes sense to run this unconditionally before we run other "spatch" rules as a basic sanity check. See 1. 803394459d4 (t/Makefile: add machinery to check correctness of chainlint.sed, 2018-07-11) Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com> --- Makefile | 2 ++ 1 file changed, 2 insertions(+)