From: <wen.yang99@zte.com.cn>
To: <Markus.Elfring@web.de>
Cc: michal.lkml@markovi.net, nicolas.palix@imag.fr,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
cocci@systeme.lip6.fr
Subject: Re: [Cocci] Coccinelle: semantic patch for missing of_node_put
Date: Tue, 4 Jun 2019 16:55:04 +0800 (CST) [thread overview]
Message-ID: <201906041655048641633@zte.com.cn> (raw)
In-Reply-To: <1bc40e20-d4d0-77e6-67d6-2230e8026ef0@web.de>
[-- Attachment #1.1: Type: text/plain, Size: 733 bytes --]
> > We currently use the following Ocaml script to automatically
> > collect functions that need to be considered.
> >
> > @initialize:ocaml@
> > @@
> >
> > let relevant_str = "use of_node_put() on it when done"
>
> I suggest to reconsider this search pattern.
>
> The mentioned words are distributed over text lines in the discussed
> software documentation.
> Thus I imagine that an other documentation format would be safer
> and more helpful for the determination of a corresponding API
> system property.
Our script will remove '* ','\ n','\t' and so on from the comments in the function header
and then merge them into one line, so we can exactly match the target string
'use of_node_put() on it when done '
--
Regards,
Wen
[-- Attachment #2: Type: text/plain, Size: 136 bytes --]
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2019-06-04 8:55 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201905171432571474636@zte.com.cn>
2019-05-17 7:14 ` Coccinelle: semantic patch for missing of_node_put Julia Lawall
2019-05-17 8:22 ` [Cocci] " Markus Elfring
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 ` [Cocci] " Julia Lawall
2019-05-20 9:52 ` Julia Lawall
2019-05-20 17:20 ` [Cocci] " Sasha Levin
2019-05-20 17:20 ` Sasha Levin
2019-05-20 19:53 ` [Cocci] " Julia Lawall
2019-05-20 19:53 ` Julia Lawall
2019-05-20 20:11 ` [Cocci] " Markus Elfring
2019-05-20 20:11 ` Markus Elfring
2019-05-17 8:10 ` [Cocci] " Markus Elfring
2019-05-17 8:10 ` Markus Elfring
2019-05-18 14:43 ` [Cocci] " Markus Elfring
2019-05-18 14:43 ` Markus Elfring
2019-06-04 5:08 ` [Cocci] " Markus Elfring
2019-06-04 5:08 ` Markus Elfring
2019-06-04 5:50 ` [Cocci] " wen.yang99
2019-06-04 6:36 ` Markus Elfring
2019-06-04 6:36 ` Markus Elfring
2019-06-04 8:55 ` wen.yang99 [this message]
2019-06-04 9:08 ` [Cocci] " Markus Elfring
2019-06-04 9:08 ` Markus Elfring
2019-06-04 11:28 ` [Cocci] " Markus Elfring
2019-06-04 11:28 ` Markus Elfring
2019-06-05 18:23 ` [Cocci] Coccinelle: Searching for “when done” in function comments Markus Elfring
2019-06-05 18:23 ` Markus Elfring
2019-05-09 1:47 [Cocci] [PATCH] coccinelle: semantic patch for missing of_node_put wen.yang99
2019-05-09 8:10 ` [Cocci] Coccinelle: " 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=201906041655048641633@zte.com.cn \
--to=wen.yang99@zte.com.cn \
--cc=Markus.Elfring@web.de \
--cc=cocci@systeme.lip6.fr \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=nicolas.palix@imag.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.