[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.02.1506140900580.2085@localhost6.localdomain6>
Date: Sun, 14 Jun 2015 09:02:24 +0200 (CEST)
From: Julia Lawall <julia.lawall@...6.fr>
To: Nicholas Mc Guire <hofrat@...dl.org>
cc: Julia Lawall <Julia.Lawall@...6.fr>,
Gilles Muller <Gilles.Muller@...6.fr>,
Nicolas Palix <nicolas.palix@...g.fr>,
Michal Marek <mmarek@...e.cz>, Joe Perches <joe@...ches.com>,
Andy Whitcroft <apw@...onical.com>,
John Stultz <john.stultz@...aro.org>, cocci@...teme.lip6.fr,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH RFC V2] coccinelle: flag constants being passed for
jiffies
> +@...ipt: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
> +@...ipt: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
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists