[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1339615857.28729.6.camel@joe2Laptop>
Date: Wed, 13 Jun 2012 12:30:57 -0700
From: Joe Perches <joe@...ches.com>
To: Andy Whitcroft <apw@...onical.com>
Cc: Peter Zijlstra <peterz@...radead.org>,
Vincent Guittot <vincent.guittot@...aro.org>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linaro-dev@...ts.linaro.org, devicetree-discuss@...ts.ozlabs.org,
linux@....linux.org.uk, grant.likely@...retlab.ca,
rob.herring@...xeda.com
Subject: Re: [RFC 1/4] ARM: topology: Add arch_scale_freq_power function
On Wed, 2012-06-13 at 20:27 +0100, Andy Whitcroft wrote:
> On Wed, Jun 13, 2012 at 02:52:49PM +0200, Peter Zijlstra wrote:
> > On Tue, 2012-06-12 at 14:02 +0200, Vincent Guittot wrote:
> > > }
> > > smp_wmb();
> > > }
> >
> > You know what.. we should make checkpatch report an error for memory
> > barriers that don't have a comment.
> >
> > I know this isn't added by this patch, but every time I see something
> > like it I cry a little.
>
> Actually if it was a new line, it would have been reported, at least in
> theory:
>
> # check for memory barriers without a comment.
> if ($line =~
> /\b(mb|rmb|wmb|read_barrier_depends|smp_mb|smp_rmb|smp_wmb|smp_read_barrier_depends)\(/)
> {
> if (!ctx_has_comment($first_line, $linenr)) {
> CHK("MEMORY_BARRIER",
> "memory barrier without comment\n" . $herecurr);
> }
> }
Maybe promote that CHK to a WARN.
--
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