From: Benjamin Philip <benjamin.philip495@gmail.com>
To: Julia Lawall <Julia.Lawall@inria.fr>,
Nicolas Palix <nicolas.palix@imag.fr>,
Jonathan Corbet <corbet@lwn.net>
Cc: cocci@inria.fr, workflows@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Benjamin Philip <benjamin.philip495@gmail.com>
Subject: [PATCH 0/3] scripts: coccicheck: document debug log handling
Date: Sun, 28 Dec 2025 11:31:22 -0800 [thread overview]
Message-ID: <CAMEXYWegtqikPYBRaZcpd_JwQPH80cXhaRK66J8ZhWPrYc7-yw@mail.gmail.com> (raw)
Currently 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.
This patchset documents this behaviour in both the coccicheck script as well as
in the dev-tools documentation. Additionally, it simplifies some of the logic
for handling debug files.
Benjamin Philip (3):
scripts: coccicheck: simplify debug file handling
scripts: coccicheck: warn on unset debug file
Documentation: Coccinelle: document debug log handling
Documentation/dev-tools/coccinelle.rst | 21 ++++++++++++++++-----
scripts/coccicheck | 21 +++++++++++++--------
2 files changed, 29 insertions(+), 13 deletions(-)
--
2.52.0
next reply other threads:[~2025-12-28 19:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-28 19:31 Benjamin Philip [this message]
2025-12-28 19:34 ` [PATCH 1/3] scripts: coccicheck: simplify debug file handling Benjamin Philip
[not found] ` <20251228193417.1143676-1-benjamin.philip495@gmail.com>
2025-12-28 19:34 ` [PATCH 2/3] scripts: coccicheck: warn on unset debug file Benjamin Philip
2025-12-28 19:36 ` Benjamin Philip
2025-12-28 19:36 ` [PATCH 3/3] Documentation: Coccinelle: document debug log handling Benjamin Philip
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=CAMEXYWegtqikPYBRaZcpd_JwQPH80cXhaRK66J8ZhWPrYc7-yw@mail.gmail.com \
--to=benjamin.philip495@gmail.com \
--cc=Julia.Lawall@inria.fr \
--cc=cocci@inria.fr \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.palix@imag.fr \
--cc=workflows@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox