From: Andrew Morton <akpm@linux-foundation.org>
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: Dmitri Vorobiev <dmitri.vorobiev@gmail.com>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] saa7146: fix sparse warnings
Date: Sun, 2 Mar 2008 11:57:43 -0800 [thread overview]
Message-ID: <20080302115743.c9a0a280.akpm@linux-foundation.org> (raw)
In-Reply-To: <1204481204.23005.8.camel@brick>
On Sun, 02 Mar 2008 10:06:44 -0800 Harvey Harrison <harvey.harrison@gmail.com> wrote:
> On Sun, 2008-03-02 at 20:34 +0300, Dmitri Vorobiev wrote:
> > Harvey Harrison пишет:
> > >
> > > - if( 0 != (dev->ext)) {
> > > + if( NULL != (dev->ext)) {
> >
> > At the risk of looking an idiot, I'm taking a liberty to ask what is
> > the point in explicit comparison to zero in conditional operators? Is
> > it not a fundamental C idiom to write
>
> <snip>
>
> Yes, that's how I would have written it, but I tried to keep with the
> prevailing style in that file.
I'm not a bit fan of the match-the-existing-style approach.
You'll find that files which started out with a non-standard style already
contain a mixup of styles, because later changes were often made in
standard-style.
And given that we're churning the code anyway, we might as well fix it up now.
Yes, that'll make the code look partially-weird rather than wholly-weird,
but I doubt if that will harm anyone much.
prev parent reply other threads:[~2008-03-02 20:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 17:52 [PATCH] saa7146: fix sparse warnings Harvey Harrison
2008-02-21 21:19 ` Al Viro
2008-02-21 21:22 ` Harvey Harrison
2008-03-02 17:34 ` Dmitri Vorobiev
2008-03-02 18:06 ` Harvey Harrison
2008-03-02 18:46 ` Dmitri Vorobiev
2008-03-02 19:57 ` Andrew Morton [this message]
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=20080302115743.c9a0a280.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dmitri.vorobiev@gmail.com \
--cc=harvey.harrison@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
/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