From: "Tony Battersby" <tonyb@cybernetics.com>
To: 'Matthew Dharm' <mdharm-scsi@one-eyed-alien.net>
Cc: linux-scsi@vger.kernel.org
Subject: RE: [PATCH] kill of ->command
Date: Mon, 9 Jun 2003 15:19:43 -0400 [thread overview]
Message-ID: <000701c32ebc$15c8b3f0$e0019d89@cybernetics.com> (raw)
In-Reply-To: <20030609114515.D5618@one-eyed-alien.net>
> BTW, is NULL == (void*)0 everywhere? I seem to recall places where it
> isn't....
>From the recesses of my memory, NULL is always equivalent to (void*)0, but
that doesn't necessarily mean that a NULL pointer has a bit pattern of all
zeros as stored in the computer's memory. NULL is replaced with (void*)0 by
the preprocessor, and then the compiler for the target architecture
determines the appropriate bit pattern for (void*)0. You can think of
(void*)0 as just a name for the null pointer which doesn't determine its
actual value. On some old architectures, memset to zero does not
automatically set pointers to NULL. I do not remember the specific
architectures which are affected, but I doubt Linux runs or will ever run on
any of them.
For modern code, it is safe to assume that memset to zero will set pointers
to NULL.
Anthony J. Battersby
Cybernetics
prev parent reply other threads:[~2003-06-09 19:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-09 16:20 [PATCH] kill of ->command Christoph Hellwig
2003-06-09 16:41 ` Patrick Mansfield
2003-06-09 16:51 ` Christoph Hellwig
2003-06-09 18:04 ` Patrick Mansfield
2003-06-09 18:11 ` Christoph Hellwig
2003-06-09 18:15 ` Russell King
2003-06-09 18:19 ` James Bottomley
2003-06-09 18:22 ` Russell King
2003-06-09 18:32 ` Matthew Dharm
2003-06-09 18:34 ` Christoph Hellwig
2003-06-09 18:37 ` Jeff Garzik
2003-06-09 18:45 ` Matthew Dharm
2003-06-09 19:05 ` Jeff Garzik
2003-06-09 19:19 ` Tony Battersby [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='000701c32ebc$15c8b3f0$e0019d89@cybernetics.com' \
--to=tonyb@cybernetics.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mdharm-scsi@one-eyed-alien.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