From: Julia Lawall <julia.lawall@inria.fr>
To: Benjamin Philip <benjamin.philip495@gmail.com>
Cc: Julia Lawall <Julia.Lawall@inria.fr>,
Nicolas Palix <nicolas.palix@imag.fr>,
Jonathan Corbet <corbet@lwn.net>,
cocci@inria.fr, workflows@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [cocci] [PATCH RESEND 0/3] scripts: coccicheck: document debug log handling
Date: Sat, 21 Feb 2026 17:40:33 +0100 (CET) [thread overview]
Message-ID: <905ec76f-027-c71-5154-76d8c4e7dbc8@inria.fr> (raw)
In-Reply-To: <20260106190836.36630-1-benjamin.philip495@gmail.com>
On Wed, 7 Jan 2026, Benjamin Philip wrote:
> 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.
All applied, thanks.
julia
>
> 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
>
>
prev parent reply other threads:[~2026-02-21 16:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 19:08 Benjamin Philip
2026-01-06 19:08 ` [PATCH RESEND 1/3] scripts: coccicheck: simplify debug file handling Benjamin Philip
2026-01-06 19:08 ` [PATCH RESEND 2/3] scripts: coccicheck: warn on unset debug file Benjamin Philip
2026-01-06 19:08 ` [PATCH RESEND 3/3] Documentation: Coccinelle: document debug log handling Benjamin Philip
2026-01-20 12:32 ` [cocci] [PATCH RESEND 0/3] scripts: coccicheck: " Julia Lawall
2026-02-21 16:40 ` Julia Lawall [this message]
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=905ec76f-027-c71-5154-76d8c4e7dbc8@inria.fr \
--to=julia.lawall@inria.fr \
--cc=benjamin.philip495@gmail.com \
--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