[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <14f4d5dc-f3b1-5cfa-4a2b-046516369fc4@web.de>
Date: Tue, 16 Jul 2019 14:05:41 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Julia Lawall <julia.lawall@...6.fr>, cocci@...teme.lip6.fr,
kernel-janitors@...r.kernel.org
Cc: Wen Yang <wen.yang99@....com.cn>, linux-kernel@...r.kernel.org,
Xue Zhihong <xue.zhihong@....com.cn>,
Yi Wang <wang.yi59@....com.cn>,
Cheng Shengyu <cheng.shengyu@....com.cn>,
Gilles Muller <Gilles.Muller@...6.fr>,
Nicolas Palix <nicolas.palix@...g.fr>,
Michal Marek <michal.lkml@...kovi.net>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
Wen Yang <yellowriver2010@...mail.com>
Subject: Re: [v3] coccinelle: semantic code search for missing of_node_put
>> 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
Powered by blists - more mailing lists