[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMEXYWdHGz4mdzc2jc7oSdqQPXLtsKktJfi_MZ0GuQRzQhURvQ@mail.gmail.com>
Date: Sun, 28 Dec 2025 11:36:43 -0800
From: Benjamin Philip <benjamin.philip495@...il.com>
To: Julia Lawall <Julia.Lawall@...ia.fr>, Nicolas Palix <nicolas.palix@...g.fr>,
Jonathan Corbet <corbet@....net>
Cc: cocci@...ia.fr, workflows@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, Benjamin Philip <benjamin.philip495@...il.com>
Subject: [PATCH 2/3] scripts: coccicheck: warn on unset debug file
coccicheck prints debug logs to stdout unless a debug file has been set.
This makes it hard to read coccinelle's suggested changes, especially
for someone new to coccicheck.
>From this commit, we warn about this behaviour from within the script on
an unset debug file. Explicitly setting the debug file to /dev/null
suppresses the warning while keeping the default.
Signed-off-by: Benjamin Philip <benjamin.philip495@...il.com>
---
scripts/coccicheck | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/scripts/coccicheck b/scripts/coccicheck
index 2efb74afef2b..8dd766009de1 100755
--- a/scripts/coccicheck
+++ b/scripts/coccicheck
@@ -260,6 +260,11 @@ coccinelle () {
}
if [ "$DEBUG_FILE" = "" ]; then
+ echo 'You have not explicitly specified the debug file to use.'
+ echo 'Using default "/dev/null" as debug file.'
+ echo 'Debug logs will be printed to stdout.'
+ echo 'You can specify the debug file with "make coccicheck
DEBUG_FILE=<debug_file>"'
+ echo ''
DEBUG_FILE="/dev/null"
fi
--
2.52.0
Powered by blists - more mailing lists