From: Markus Elfring <Markus.Elfring@web.de>
To: Wen Yang <wen.yang99@zte.com.cn>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
linux-pm@vger.kernel.org, kernel-janitors@vger.kernel.org
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Cheng Shengyu <cheng.shengyu@zte.com.cn>,
Kumar Gala <galak@kernel.crashing.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Paul Mackerras <paulus@samba.org>, Scott Wood <oss@buserror.net>,
Xue Zhihong <xue.zhihong@zte.com.cn>,
Yi Wang <wang.yi59@zte.com.cn>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: Coccinelle: Checking of_node_put() calls with SmPL
Date: Wed, 10 Jul 2019 17:15:33 +0200 [thread overview]
Message-ID: <9d515026-5b74-cf0c-0c64-4fe242d4104e@web.de> (raw)
In-Reply-To: <201907101533443009168@zte.com.cn>
> we developed a coccinelle script to detect such problems.
Would you find the implementation of the function “dt_init_idle_driver”
suspicious according to discussed source code search patterns?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/cpuidle/dt_idle_states.c?id=e9a83bd2322035ed9d7dcf35753d3f984d76c6a5#n208
https://elixir.bootlin.com/linux/v5.2/source/drivers/cpuidle/dt_idle_states.c#L208
> This script is still being improved.
Will corresponding software development challenges become more interesting?
Regards,
Markus
next parent reply other threads:[~2019-07-10 15:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201907101533443009168@zte.com.cn>
2019-07-10 15:15 ` Markus Elfring [this message]
[not found] <201907111435459627761@zte.com.cn>
2019-07-11 6:46 ` Coccinelle: Checking of_node_put() calls with SmPL Julia Lawall
2019-07-11 9:33 ` Markus Elfring
2019-07-11 9:04 ` Markus Elfring
2019-07-11 14:41 ` Tyrel Datwyler
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=9d515026-5b74-cf0c-0c64-4fe242d4104e@web.de \
--to=markus.elfring@web.de \
--cc=benh@kernel.crashing.org \
--cc=cheng.shengyu@zte.com.cn \
--cc=daniel.lezcano@linaro.org \
--cc=galak@kernel.crashing.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=oss@buserror.net \
--cc=paulus@samba.org \
--cc=rjw@rjwysocki.net \
--cc=wang.yi59@zte.com.cn \
--cc=wen.yang99@zte.com.cn \
--cc=xue.zhihong@zte.com.cn \
/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).