From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] how to find missing initializer
Date: Fri, 4 Dec 2015 09:55:29 +0100 [thread overview]
Message-ID: <56615501.4070200@users.sourceforge.net> (raw)
In-Reply-To: <56603DC3.8040609@hurleysoftware.com>
> So trying to find those in-tree drivers which _do not_ define a cleanup
> method with coccinelle, led to this fragment which has a parse error.
>
> Apologies if my question is obvious or trivial;
Your support request is fine. - You show just another interesting use case.
The preferred approach is mostly not so obvious for things you find
to be missing.
> I'm still learning coccinelle.
It is usual that it will take some time to become familiar to express
better solutions also with another programming language.
My knowledge is still evolving ?
There are more software development challenges to consider for
the semantic patch language around the handling of function pointers,
aren't there?
Regards,
Markus
prev parent reply other threads:[~2015-12-04 8:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 13:04 [Cocci] how to find missing initializer Peter Hurley
2015-12-03 18:46 ` Lars-Peter Clausen
2015-12-03 22:12 ` Julia Lawall
2015-12-03 23:48 ` Luis R. Rodriguez
2015-12-04 13:55 ` [Cocci] Searching with SmPL for missing clean-up settings in designated initialisers SF Markus Elfring
2015-12-04 14:44 ` Julia Lawall
2015-12-04 15:42 ` SF Markus Elfring
2015-12-04 11:31 ` [Cocci] how to find missing initializer SF Markus Elfring
2015-12-04 13:18 ` Julia Lawall
2015-12-04 11:54 ` Peter Hurley
2015-12-03 19:26 ` Luis R. Rodriguez
2015-12-04 8:55 ` SF 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=56615501.4070200@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=cocci@systeme.lip6.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.