All of lore.kernel.org
 help / color / mirror / Atom feed
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: Thu, 12 Jun 2025 14:54:06 +0200	[thread overview]
Message-ID: <45eb943d-1ae3-439c-8b05-7c355a54c48d@web.de> (raw)
In-Reply-To: <9eeab48f-1bc7-4395-b998-6a49330cfc2b@web.de>

>> 2) The proper scientific method is to cange only one thing at a time.
> Can any software developers determine the concrete command which would perform
> the indicated “Grep query”?

I got the impression that a function like “interpret” contains interesting
implementation details.
https://gitlab.inria.fr/coccinelle/coccinelle/-/blob/582d2ebd4543dd7febf0670f4a104679ec8bbc2d/parsing_cocci/git_grep.ml#L9-35
https://github.com/coccinelle/coccinelle/blob/4093aad2da23ea5c86916de0a71f43032fc2bb2f/parsing_cocci/git_grep.ml#L9-L23

Some data processing results can be produced accordingly.

Markus_Elfring@Sonne:/home/altes_Heim2/elfring/Projekte/Linux/next-analyses/drivers/infiniband/hw/cxgb4> git grep -l -w kfree '*.c' | rg -v .in | rg device
device.c

Markus_Elfring@Sonne:/home/altes_Heim2/elfring/Projekte/Linux/next-analyses/drivers/infiniband> git grep -l -w kfree '*.c' | rg -v .in | rg cxgb4/device
hw/cxgb4/device.c

Markus_Elfring@Sonne:/home/altes_Heim2/elfring/Projekte/Linux/next-analyses/drivers> git grep -l -w kfree '*.c' | rg -v .in | rg cxgb4/device


Would you become interested to clarify why I do not see another search result here
(while the program “spatch” would still generate an expected diff output for
the selected directory)?

Regards,
Markus

  reply	other threads:[~2025-06-12 12:54 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
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 [this message]
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=45eb943d-1ae3-439c-8b05-7c355a54c48d@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.