[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1512159257.19952.167.camel@perches.com>
Date: Fri, 01 Dec 2017 12:14:17 -0800
From: Joe Perches <joe@...ches.com>
To: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
linux-kernel@...r.kernel.org
Cc: mingo@...nel.org, jiangshanlai@...il.com, dipankar@...ibm.com,
akpm@...ux-foundation.org, mathieu.desnoyers@...icios.com,
josh@...htriplett.org, tglx@...utronix.de, peterz@...radead.org,
rostedt@...dmis.org, dhowells@...hat.com, edumazet@...gle.com,
fweisbec@...il.com, oleg@...hat.com,
Andy Whitcroft <apw@...onical.com>
Subject: Re: [PATCH tip/core/rcu 20/21] checkpatch: Add warnings for
{smp_,}read_barrier_depends()
On Fri, 2017-12-01 at 11:51 -0800, Paul E. McKenney wrote:
> Now that both smp_read_barrier_depends() and read_barrier_depends()
> are being de-emphasized, warn if any are added.
This would also warn on existing files when run
with ./scripts/checkpatch.pl -f <file>
Do you want it to check new patches only?
If so the test could become "if (!$file && etc...)
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index 95cda3ecc66b..25f7098e2ad3 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -5586,6 +5586,12 @@ sub process {
> }
> }
>
> +# check for smp_read_barrier_depends and read_barrier_depends
> + if ($line =~ /\b(smp_|)read_barrier_depends\(/) {
Must become
+ if ($line =~ /\b(smp_|)read_barrier_depends\s*\(/) {
similar to the lines above this as there are sometimes
spaces between function name and argument parentheses.
Powered by blists - more mailing lists