[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8bd0f97a0708010303j7f443b06lf9d77f6d36816237@mail.gmail.com>
Date: Wed, 1 Aug 2007 06:03:16 -0400
From: "Mike Frysinger" <vapier.adi@...il.com>
To: "Richard Knutsson" <ricknu-0@...dent.ltu.se>
Cc: "Robin Getz" <rgetz@...ckfin.uclinux.org>,
"Yoann Padioleau" <padator@...adoo.fr>,
"David Howells" <dhowells@...hat.com>,
kernel-janitors@...r.kernel.org, akpm@...ux-foundation.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 06/68] 0 -> NULL, for arch/frv
On 7/31/07, Richard Knutsson <ricknu-0@...dent.ltu.se> wrote:
> Mike Frysinger wrote:
> > On 7/27/07, Robin Getz <rgetz@...ckfin.uclinux.org> wrote:
> >> If there is a definite style or semantic preference that everyone should live
> >> with - does it make sense to put checks in checkpatch.pl to enforce it?
> >
> > checkpatch.pl does not have enough semantic knowledge to know if the
> > thing being tested is a pointer ... dont know if the sparse utility
> > would be able to pick it out as i'm not familiar with what level that
> > thing runs at
>
> Didn't he mean "x == NULL" > "!x"?
i'm sure i understand your meaning of ">" ... are you saying that "x
== NULL" is greater (preferred) to "!x" or are you saying that "x ==
NULL" should be changed to "!x" ?
i dont think the former case can be checked by checkpatch.pl, but the
latter certainly can ... but i'd be very skeptical you could get the
wider LKML audience to sign off one way or the other wrt to "x ==
NULL" vs "!x". you can certainly get people to sign off on "x == 0"
being wrong when x is a pointer.
-mike
-
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