From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>, cocci@inria.fr
Subject: Re: [cocci] Checking another deletion of redundant null pointer checks (with SmPL)?
Date: Tue, 10 Jun 2025 18:15:27 +0200 [thread overview]
Message-ID: <629fa64c-ccd0-46ba-907c-97bebc00fa0c@web.de> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2506101739440.4658@hadrien>
> Could yo uplease make a small effort to make your reports understandable?
Why do the presented test commands trigger undesirable understanding difficulties?
> 1) I don't ned to know the paths of your files? This adds a lot of
> clutter that makes it hard to find the important information.
I find the mentioned test data relevant for further clarifications.
> 2) The proper scientific method is to cange only one thing at a time.
There are two data processing results to compare.
> You seem tohave changed two things 1: in one case you give the specific file name
Something looks reasonable.
> andin the second case you use the whole Linux kernel directory,
Yes.
The mentioned log file contains the following information then:
“…
7675 files match
…”
May I expect that a file name like “./drivers/infiniband/hw/cxgb4/device.c”
should occur there?
> and 2; in one case you are using linux-next from a specific date andin the
> other case there is no information about what kernel version you are
> using.
The mentioned test cases refer to the same Linux development repository.
Regards,
Markus
next prev parent reply other threads:[~2025-06-10 16:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 8:55 [cocci] Checking another deletion of redundant null pointer checks (with SmPL)? Markus Elfring
2025-06-10 15:43 ` Julia Lawall
2025-06-10 16:15 ` Markus Elfring [this message]
2025-06-10 16:32 ` Julia Lawall
2025-06-10 16:40 ` Markus Elfring
[not found] ` <alpine.DEB.2.22.394.2506101850030.4658@hadrien>
2025-06-10 17:00 ` Markus Elfring
[not found] ` <alpine.DEB.2.22.394.2506101925310.4658@hadrien>
2025-06-10 18:33 ` Markus Elfring
2025-06-11 5:50 ` Markus Elfring
2025-06-12 10:40 ` Markus Elfring
2025-06-11 17:55 ` Markus Elfring
2025-06-12 12:54 ` Markus Elfring
2025-06-12 13:02 ` Julia Lawall
2025-06-12 14:23 ` Markus Elfring
2025-06-12 15:54 ` Keller, Jacob E
2025-06-12 16:04 ` Julia Lawall
2025-06-12 16:13 ` Keller, Jacob E
2025-06-13 8:46 ` Markus Elfring
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=629fa64c-ccd0-46ba-907c-97bebc00fa0c@web.de \
--to=markus.elfring@web.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox