From: Markus Elfring <Markus.Elfring@web.de>
To: Mats Kindahl <mats.kindahl@gmail.com>, cocci@inria.fr
Subject: Re: [cocci] Detecting missing resource releases (with SmPL)?
Date: Thu, 19 Dec 2024 10:52:48 +0100 [thread overview]
Message-ID: <79ebcaff-826f-410b-91c8-7659942d9f56@web.de> (raw)
In-Reply-To: <f0764391-b0d3-48fa-8a54-6edddf8d2c8d@gmail.com>
> Anybody have some insight
Probably, yes.
Which information sources should get more development attention?
> into what I've done wrong
Some circumstances can make your source code analysis attempts more challenging.
> or if there is a better way to solve this problem?
Further software design possibilities can be taken better into account.
How will technical aspects be clarified accordingly?
Regards,
Markus
next prev parent reply other threads:[~2024-12-19 9:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 7:25 [cocci] Depends on with negative matches Mats Kindahl
2024-12-19 7:53 ` Julia Lawall
2024-12-19 18:55 ` Mats Kindahl
2024-12-19 19:54 ` Markus Elfring
2024-12-20 21:54 ` Julia Lawall
2024-12-21 9:08 ` Markus Elfring
2024-12-21 14:24 ` Mats Kindahl
2024-12-21 14:25 ` Julia Lawall
2024-12-21 16:14 ` Markus Elfring
2024-12-19 9:52 ` Markus Elfring [this message]
2024-12-19 11:32 ` [cocci] Scope for source code analyses (with SmPL)? 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=79ebcaff-826f-410b-91c8-7659942d9f56@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.fr \
--cc=mats.kindahl@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