From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@lip6.fr>,
cocci@systeme.lip6.fr, kernel-janitors@vger.kernel.org
Cc: Yi Wang <wang.yi59@zte.com.cn>,
Michal Marek <michal.lkml@markovi.net>,
Wen Yang <yellowriver2010@hotmail.com>,
Nicolas Palix <nicolas.palix@imag.fr>,
linux-kernel@vger.kernel.org,
Xue Zhihong <xue.zhihong@zte.com.cn>,
Cheng Shengyu <cheng.shengyu@zte.com.cn>,
Wen Yang <wen.yang99@zte.com.cn>
Subject: Re: [Cocci] [v3] coccinelle: semantic code search for missing of_node_put
Date: Tue, 16 Jul 2019 14:05:41 +0200 [thread overview]
Message-ID: <14f4d5dc-f3b1-5cfa-4a2b-046516369fc4@web.de> (raw)
In-Reply-To: <alpine.DEB.2.21.1907161307550.2885@hadrien>
>> Why would you like to keep this SmPL code in the commit description?
>
> I don't know indetail what you are proposing,
I imagine that you can get more interesting software development ideas
from links to previous messages.
I hope that the desired clarification can become more constructive.
How are the chances to move such code into SmPL script files?
> but I would prefer not to put semantic patches that involve iteration
> into the kernel, for simplicity.
This view is also interesting.
But I hope that this functionality will become more helpful
if we can agree on value combinations which should be iterated
for powerful source code analysis.
>> I would prefer software evolution in an other direction.
>> https://lore.kernel.org/lkml/44be5924-26ca-5106-aa25-3cbc3343aa2c@web.de/
>> https://lkml.org/lkml/2019/7/4/21
Would you like to add any more advices for affected software components?
Regards,
Markus
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2019-07-16 12:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-16 3:05 [Cocci] [PATCH v3] coccinelle: semantic code search for missing of_node_put Wen Yang
2019-07-16 9:25 ` Markus Elfring
2019-07-16 11:08 ` Julia Lawall
2019-07-16 12:05 ` [Cocci] [v3] " Markus Elfring
2019-07-16 12:05 ` Markus Elfring [this message]
2019-07-17 3:43 ` [Cocci] [PATCH v3] coccinelle: semantic code search for missingof_node_put wen.yang99
2019-07-17 8:00 ` [Cocci] [v3] coccinelle: semantic code search for missing of_node_put Markus Elfring
2019-07-18 12:54 ` [Cocci] [v3] Coccinelle: semantic code search for “use after …” Markus Elfring
2019-07-18 12:54 ` 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=14f4d5dc-f3b1-5cfa-4a2b-046516369fc4@web.de \
--to=markus.elfring@web.de \
--cc=cheng.shengyu@zte.com.cn \
--cc=cocci@systeme.lip6.fr \
--cc=julia.lawall@lip6.fr \
--cc=kernel-janitors@vger.kernel.org \
--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=xue.zhihong@zte.com.cn \
--cc=yellowriver2010@hotmail.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;
as well as URLs for NNTP newsgroup(s).