From: Jakub Kicinski <kuba@kernel.org>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: cocci@inria.fr
Subject: [cocci] spatch --use-patch-diff broken?
Date: Mon, 5 Feb 2024 09:56:37 -0800 [thread overview]
Message-ID: <20240205095637.54f3f450@kernel.org> (raw)
Hi!
I've been trying to run coccicheck with --use-patch-diff
to try to limit the number of processed files. I _think_
it worked when I set it up early last month but recently
I went back to check and make coccicheck stops after
the first spatch call, all it prints is "hd"
https://netdev-3.bots.linux.dev/cocci/results/452585/new
spatch seems to work fine when run without --use-patch-diff
cocci version is the latest from git as of $now
FWIW the git hashes are from this tree:
https://github.com/linux-netdev/testing.git
(probably best to clone that thing with --depth $number)
Example:
/usr/local/bin/spatch -D report --no-show-diff --very-quiet --cocci-file ./scripts/coccinelle/api/err_cast.cocci --no-includes --include-headers --dir . -I ./arch/x86/include -I ./arch/x86/include/generated -I ./include -I ./arch/x86/include/uapi -I ./arch/x86/include/generated/uapi -I ./include/uapi -I ./include/generated/uapi --include ./include/linux/compiler-version.h --include ./include/linux/kconfig.h --jobs 48 --chunksize 1 --use-patch-diff b9f2444cd114a7f9c44950dc850aa1753b3edd94..be5bf59888403413619dd74e0d5f5386ffafbc90
grep: warning: + at start of expression
grep: warning: + at start of expression
grep: warning: + at start of expression
hd
next reply other threads:[~2024-02-06 14:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 17:56 Jakub Kicinski [this message]
2024-02-05 19:38 ` [cocci] spatch --use-patch-diff broken? Julia Lawall
2024-02-05 19:39 ` Julia Lawall
2024-02-05 20:02 ` Jakub Kicinski
2024-02-05 22:37 ` Julia Lawall
2024-02-05 23:36 ` Jakub Kicinski
2024-02-06 11:31 ` Julia Lawall
2024-02-06 13:58 ` Julia Lawall
2024-02-06 15:14 ` Jakub Kicinski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240205095637.54f3f450@kernel.org \
--to=kuba@kernel.org \
--cc=cocci@inria.fr \
--cc=julia.lawall@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.