[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1491494308.27353.99.camel@perches.com>
Date: Thu, 06 Apr 2017 08:58:28 -0700
From: Joe Perches <joe@...ches.com>
To: Peter Zijlstra <peterz@...radead.org>,
Darren Hart <dvhart@...radead.org>
Cc: tglx@...utronix.de, mingo@...nel.org, juri.lelli@....com,
rostedt@...dmis.org, xlpang@...hat.com, bigeasy@...utronix.de,
linux-kernel@...r.kernel.org, mathieu.desnoyers@...icios.com,
jdesfossez@...icios.com, bristot@...hat.com
Subject: Re: [PATCH -v6 05/13] futex: Change locking rules
On Thu, 2017-04-06 at 14:28 +0200, Peter Zijlstra wrote:
> On Wed, Apr 05, 2017 at 02:18:43PM -0700, Darren Hart wrote:
> > On Wed, Mar 22, 2017 at 11:35:52AM +0100, Peter Zijlstra wrote:
> > > @@ -1336,6 +1418,7 @@ static int wake_futex_pi(u32 __user *uad
> > >
> > > if (cmpxchg_futex_value_locked(&curval, uaddr, uval, newval)) {
> > > ret = -EFAULT;
> > > +
> >
> > Stray whitespace addition? Not explicitly against coding-style, but I don't
> > normally see a new line before the closing brace leading to an else...
>
> I found it more readable that way. Sod checkpatch and co ;-)
The only good sod is the stuff you get to play games on.
And this week's best sod is Augusta's immaculate carpet
for the Masters Tournament.
So no worries from me. checkpatch is a brainless script.
Rules made to be broken, etc.
afaict another way to write that would be to use gotos
and that would be a lot more lines and less readable.
Powered by blists - more mailing lists