Re: [PATCH 18/68] 0 -> NULL, for arch/um

Jeff Dike <[email protected]> writes:

> On Fri, Jul 27, 2007 at 11:45:56AM +0200, Yoann Padioleau wrote:
>> When comparing a pointer, it's clearer to compare it to NULL than to 0.
>
> ACK
>
>>  sys-i386/fault.c   |    2 +-
>>  sys-x86_64/fault.c |    2 +-
>>  2 files changed, 2 insertions(+), 2 deletions(-)
>
> Except you should probably diff from the top of the kernel tree.

Sorry. I will use diffstat -p1  from now on.

>
> 				Jeff
>
> -- 
> Work email - jdike at linux dot intel dot com

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [PATCH 18/68] 0 -> NULL, for arch/um
    • From: Yoann Padioleau <[email protected]>
  • Re: [PATCH 18/68] 0 -> NULL, for arch/um
    • From: Jeff Dike <[email protected]>

• Prev by Date: Re: solving(?) the updatedb problem w/ the kernel cache
• Next by Date: [PATCH] Merge the Sonics Silicon Backplane subsystem
• Previous by thread: Re: [PATCH 18/68] 0 -> NULL, for arch/um
• Next by thread: [PATCH] Fix kobject documentation
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]