From: Yoann Padioleau <padator@wanadoo.fr>
To: Jeff Dike <jdike@addtoit.com>
Cc: Yoann Padioleau <padator@wanadoo.fr>,
kernel-janitors@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 18/68] 0 -> NULL, for arch/um
Date: Fri, 27 Jul 2007 18:49:54 +0200 [thread overview]
Message-ID: <871wet7pvx.fsf@wanadoo.fr> (raw)
In-Reply-To: <20070727163541.GA6930@c2.user-mode-linux.org> (Jeff Dike's message of "Fri, 27 Jul 2007 12:35:41 -0400")
Jeff Dike <jdike@addtoit.com> 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
prev parent reply other threads:[~2007-07-27 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 9:45 [PATCH 18/68] 0 -> NULL, for arch/um Yoann Padioleau
2007-07-27 16:35 ` Jeff Dike
2007-07-27 16:49 ` Yoann Padioleau [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=871wet7pvx.fsf@wanadoo.fr \
--to=padator@wanadoo.fr \
--cc=akpm@linux-foundation.org \
--cc=jdike@addtoit.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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