From: Julia Lawall <julia.lawall@lip6.fr>
To: Nicholas Mc Guire <hofrat@osadl.org>
Cc: Julia Lawall <Julia.Lawall@lip6.fr>,
Gilles Muller <Gilles.Muller@lip6.fr>,
Nicolas Palix <nicolas.palix@imag.fr>,
Michal Marek <mmarek@suse.cz>, Joe Perches <joe@perches.com>,
Andy Whitcroft <apw@canonical.com>,
John Stultz <john.stultz@linaro.org>,
cocci@systeme.lip6.fr, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC V2] coccinelle: flag constants being passed for jiffies
Date: Sun, 14 Jun 2015 09:02:24 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.02.1506140900580.2085@localhost6.localdomain6> (raw)
In-Reply-To: <1434128979-2096-1-git-send-email-hofrat@osadl.org>
> +@script:python depends on report@
> +p << cc.p;
> +timeout << cc.C;
> +@@
> +
> +if str.isdigit(timeout):
> + if (int(timeout) != 1):
> + msg = "WARNING: timeout (%s) seems HZ dependent" % (timeout)
> + coccilib.report.print_report(p[0], msg)
The parentheses in the warning messages around the timeouts seem a little
strange to me.
Otherwise, as a semantic patch, it looks fine. I can't judge the problem
being solved though.
julia
> +@script:python depends on strict@
> +p << cc.p;
> +timeout << cc.C;
> +@@
> +
> +# "strict" mode prints the cases that use C-constants != HZ
> +# as well as the numeric constants != 1. This will deliver a false
> +# positives if the C-constant is already in jiffies !
> +if str.isdigit(timeout):
> + if (int(timeout) != 1):
> + msg = "WARNING: timeout (%s) is HZ dependent" % (timeout)
> + coccilib.report.print_report(p[0], msg)
> +elif (timeout != "HZ"):
> + msg = "INFO: timeout (%s) may be HZ dependent" % (timeout)
> + coccilib.report.print_report(p[0], msg)
> --
> 1.7.10.4
>
>
next prev parent reply other threads:[~2015-06-14 7:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-12 17:09 Nicholas Mc Guire
2015-06-14 6:49 ` Julia Lawall
2015-06-14 7:02 ` Julia Lawall [this message]
2015-06-14 7:34 ` Nicholas Mc Guire
2015-06-14 7:44 ` Julia Lawall
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=alpine.DEB.2.02.1506140900580.2085@localhost6.localdomain6 \
--to=julia.lawall@lip6.fr \
--cc=Gilles.Muller@lip6.fr \
--cc=apw@canonical.com \
--cc=cocci@systeme.lip6.fr \
--cc=hofrat@osadl.org \
--cc=joe@perches.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=nicolas.palix@imag.fr \
/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®