From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>, cocci@inria.fr
Cc: Erick Karanja <karanja99erick@gmail.com>,
Jacob Keller <jacob.e.keller@intel.com>
Subject: Re: [cocci] Checking another deletion of redundant null pointer checks (with SmPL)?
Date: Fri, 13 Jun 2025 10:46:42 +0200 [thread overview]
Message-ID: <e6612f88-250f-4d02-8dfe-dd8afe5fa429@web.de> (raw)
In-Reply-To: <45eb943d-1ae3-439c-8b05-7c355a54c48d@web.de>
> Markus_Elfring@Sonne:…/Projekte/Linux/next-analyses/drivers> git grep -l -w kfree '*.c' | rg -v .in | rg cxgb4/device
Further collateral evolution will happen somehow.
See also:
* More precise exclusion of .in files
2025-06-12
https://gitlab.inria.fr/coccinelle/coccinelle/-/commit/c717dff248a7fcc308c007bf3c8a705cd2c39c26
* Remaining open issues according to the software component “git grep”?
Regards,
Markus
prev parent reply other threads:[~2025-06-13 8:47 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
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 [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=e6612f88-250f-4d02-8dfe-dd8afe5fa429@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.fr \
--cc=jacob.e.keller@intel.com \
--cc=julia.lawall@inria.fr \
--cc=karanja99erick@gmail.com \
/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