From: Markus Elfring <Markus.Elfring@web.de>
To: Wen Yang <wen.yang99@zte.com.cn>,
Julia Lawall <julia.lawall@lip6.fr>,
linux-doc@vger.kernel.org
Cc: cocci@systeme.lip6.fr, linux-kernel@vger.kernel.org,
Gilles Muller <Gilles.Muller@lip6.fr>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Michal Marek <michal.lkml@markovi.net>,
Nicolas Palix <nicolas.palix@imag.fr>
Subject: Re: Coccinelle: semantic patch for missing of_node_put
Date: Tue, 4 Jun 2019 07:08:35 +0200 [thread overview]
Message-ID: <fa3b24ba-1c57-3115-6a01-ee98fd702087@web.de> (raw)
In-Reply-To: <201905171432571474636@zte.com.cn>
> 2, A general method.
> We also try to get the list of functions to consider by writing a SmPL,
> but this method is not feasible at present, because it is not easy to parse the comment
> header information of these functions.
The situation was improved once more also for the Coccinelle software.
How do you think about to develop any more variants based on information
from a script (like the following) for the semantic patch language?
@initialize:python@
@@
import re, sys
filter = re.compile(" when done")
@find@
comments c;
identifier x;
type t;
@@
t@c x(...)
{ ... }
@script:python selection@
input << find.c;
@@
if filter.search(input[0].before, 2):
sys.stderr.write(input[0].before + "\n=====\n")
else:
cocci.include_match(False)
@display@
identifier find.x;
type find.t;
@@
*t x(...)
{ ... }
Does such a source code analysis approach indicate any details
which should be improved for the affected software documentation?
Regards,
Markus
next prev parent reply other threads:[~2019-06-04 5:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201905171432571474636@zte.com.cn>
2019-05-17 7:14 ` Julia Lawall
2019-05-17 8:22 ` Markus Elfring
2019-05-20 9:33 ` Pavel Machek
2019-05-20 9:51 ` Julia Lawall
2019-05-20 9:52 ` Julia Lawall
2019-05-20 17:20 ` Sasha Levin
2019-05-20 19:53 ` Julia Lawall
2019-05-20 20:11 ` Markus Elfring
2019-05-17 8:10 ` Markus Elfring
2019-05-18 14:43 ` Markus Elfring
2019-06-04 5:08 ` Markus Elfring [this message]
2019-06-05 18:23 ` Coccinelle: Searching for “when done” in function comments Markus Elfring
[not found] <201906041350002807147@zte.com.cn>
2019-06-04 6:36 ` Coccinelle: semantic patch for missing of_node_put Markus Elfring
2019-06-04 11:28 ` Markus Elfring
[not found] <201906041655048641633@zte.com.cn>
2019-06-04 9:08 ` Markus Elfring
[not found] <201905090947015772925@zte.com.cn>
2019-05-09 8:10 ` 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=fa3b24ba-1c57-3115-6a01-ee98fd702087@web.de \
--to=markus.elfring@web.de \
--cc=Gilles.Muller@lip6.fr \
--cc=cocci@systeme.lip6.fr \
--cc=julia.lawall@lip6.fr \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=nicolas.palix@imag.fr \
--cc=wen.yang99@zte.com.cn \
--cc=yamada.masahiro@socionext.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
Powered by JetHome