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 20:33:15 +0200 [thread overview]
Message-ID: <b28bb07e-00d4-464a-8efb-d2d0862998a9@web.de> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2506101925310.4658@hadrien>
>> I would appreciate to clarify if mentioned files would be completely accessible
>> for the shown source code transformation approach.
>
> The number 7675 is not going to help me understand what the problem is.
Would you expect that any diff output should appear for the source file
“drivers/infiniband/hw/cxgb4/device.c” also in the file “delete_redundant_checks4.diff”?
Which data processing results do you observe in your software test environments?
Regards,
Markus
next prev parent reply other threads:[~2025-06-10 18:33 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
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 [this message]
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=b28bb07e-00d4-464a-8efb-d2d0862998a9@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 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.