From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@lip6.fr>, Wen Yang <wen.yang99@zte.com.cn>
Cc: Yi Wang <wang.yi59@zte.com.cn>,
Gilles Muller <Gilles.Muller@lip6.fr>,
Nicolas Palix <nicolas.palix@imag.fr>,
Michal Marek <michal.lkml@markovi.net>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
cocci@systeme.lip6.fr, linux-kernel@vger.kernel.org
Subject: Re: [v2] coccinelle: semantic code search for missing of_node_put
Date: Fri, 5 Jul 2019 08:45:43 +0200 [thread overview]
Message-ID: <0972fc1d-2ed4-2f0c-ee50-d0d34f806e38@web.de> (raw)
In-Reply-To: <alpine.DEB.2.21.1907050811110.18245@hadrien>
>> @script:python depends on report && r1@
>
> No need to depend on r1. That is guaranteed by the inheritance on the
> metavariables below.
Will this information become more helpful for the completion of the corresponding
software documentation?
Regards,
Markus
next prev parent reply other threads:[~2019-07-05 6:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201907051357245235750@zte.com.cn>
2019-07-05 6:17 ` [PATCH v2] coccinelle: semantic code search formissingof_node_put Julia Lawall
2019-07-05 6:45 ` Markus Elfring [this message]
[not found] <201907041103003504524@zte.com.cn>
2019-07-04 6:28 ` [v2] coccinelle: semantic code search for missing of_node_put Markus Elfring
[not found] <201907041041053843118@zte.com.cn>
2019-07-04 5:40 ` Markus Elfring
2019-06-28 2:58 [PATCH v2] " Wen Yang
2019-06-28 9:38 ` Markus Elfring
2019-06-28 11:07 ` Julia Lawall
2019-06-28 14:16 ` [v2] " Markus Elfring
2019-06-28 14:16 ` Markus Elfring
2019-06-29 7:40 ` Markus Elfring
2019-06-29 7:49 ` Julia Lawall
2019-06-29 8:35 ` 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=0972fc1d-2ed4-2f0c-ee50-d0d34f806e38@web.de \
--to=markus.elfring@web.de \
--cc=Gilles.Muller@lip6.fr \
--cc=cocci@systeme.lip6.fr \
--cc=julia.lawall@lip6.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=nicolas.palix@imag.fr \
--cc=wang.yi59@zte.com.cn \
--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
all inboxes | Powered by JetHome®