From: Markus Elfring <Markus.Elfring@web.de>
To: Wen Yang <wenyang@linux.alibaba.com>,
cocci@systeme.lip6.fr, kernel-janitors@vger.kernel.org
Cc: "Michal Marek" <michal.lkml@markovi.net>,
"Julia Lawall" <Julia.Lawall@lip6.fr>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Nicolas Palix" <nicolas.palix@imag.fr>,
"Gilles Muller" <Gilles.Muller@lip6.fr>,
"Matthias Männich" <maennich@google.com>,
linux-kernel@vger.kernel.org,
"Thomas Gleixner" <tglx@linutronix.de>
Subject: Re: [Cocci] [PATCH v3] coccinelle: semantic patch to check for inappropriate do_div() calls
Date: Fri, 10 Jan 2020 17:35:21 +0100 [thread overview]
Message-ID: <91abb141-57b8-7659-25ec-8080e290d846@web.de> (raw)
In-Reply-To: <20200110131526.60180-1-wenyang@linux.alibaba.com>
> +@initialize:python@
…
> +def filter_out_safe_constants(str):
…
> +def construct_warnings(str, suggested_fun):
* I suggest once more to adjust the dependency specifications for the usage
of these functions by SmPL rules.
* Can the local variable “msg” be omitted?
> +coccilib.org.print_todo(p[0], construct_warnings("div64_ul"))
I suggest again to move the prefix “div64_” into the string literal
of the function implementation.
The SmPL code for two disjunctions could become shorter.
Regards,
Markus
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2020-01-10 16:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 13:15 [Cocci] [PATCH v3] coccinelle: semantic patch to check for inappropriate do_div() calls Wen Yang
2020-01-10 16:35 ` Markus Elfring [this message]
2020-01-11 5:06 ` Wen Yang
2020-01-11 7:30 ` [Cocci] [v3] " Markus Elfring
2020-01-11 7:44 ` Julia Lawall
2020-01-11 8:03 ` Markus Elfring
2020-01-11 15:36 ` [Cocci] [PATCH v3] " Julia Lawall
2020-01-12 8:30 ` Markus Elfring
2020-01-12 8:42 ` Julia Lawall
2020-01-12 8:49 ` [Cocci] [v3] " 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=91abb141-57b8-7659-25ec-8080e290d846@web.de \
--to=markus.elfring@web.de \
--cc=Gilles.Muller@lip6.fr \
--cc=Julia.Lawall@lip6.fr \
--cc=cocci@systeme.lip6.fr \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maennich@google.com \
--cc=michal.lkml@markovi.net \
--cc=nicolas.palix@imag.fr \
--cc=tglx@linutronix.de \
--cc=wenyang@linux.alibaba.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).