From: Jeff Garzik <jgarzik@pobox.com>
To: Patrick Mansfield <patmans@us.ibm.com>
Cc: Douglas Gilbert <dougg@torque.net>,
Andre Hedrick <andre@pyxtechnologies.com>,
"J. E. J. Bottomley" <James.Bottomley@SteelEye.com>,
Linus Torvalds <torvalds@transmeta.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-2.4.18-modified-scsi-h.patch
Date: Tue, 19 Nov 2002 13:47:34 -0500 [thread overview]
Message-ID: <3DDA8746.3010409@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10211182138310.2779-200000@master.linux-ide.org>
Patrick Mansfield wrote:
> I don't see why we need the #define, or is that another patch?
The define exists for the same reason that HAVE_xxx exists in
include/linux/netdevice.h and other headers: a feature test macro, so
code using this pointer can detect its presence or absence. The world
of drivers is not all in the kernel tarball, ya know ;-)
But as I said, the macro is misnamed, it should be
HAVE_UPPER_PRIVATE_DATA or similar.
Jeff
next prev parent reply other threads:[~2002-11-19 18:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-18 23:45 2.5.48 /proc/scsi directory missing Douglas Gilbert
2002-11-19 1:14 ` Patrick Mansfield
2002-11-19 6:16 ` linux-2.4.18-modified-scsi-h.patch Andre Hedrick
2002-11-19 6:28 ` linux-2.4.18-modified-scsi-h.patch Jeff Garzik
2002-11-19 6:42 ` linux-2.4.18-modified-scsi-h.patch Andre Hedrick
2002-11-19 10:11 ` linux-2.4.18-modified-scsi-h.patch Douglas Gilbert
2002-11-19 12:16 ` linux-2.4.18-modified-scsi-h.patch Andre Hedrick
2002-11-19 18:40 ` linux-2.4.18-modified-scsi-h.patch Patrick Mansfield
2002-11-19 18:48 ` linux-2.4.18-modified-scsi-h.patch Andre Hedrick
2002-11-19 18:47 ` Jeff Garzik [this message]
2002-11-19 18:50 ` linux-2.4.18-modified-scsi-h.patch Andre Hedrick
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=3DDA8746.3010409@pobox.com \
--to=jgarzik@pobox.com \
--cc=James.Bottomley@SteelEye.com \
--cc=andre@pyxtechnologies.com \
--cc=dougg@torque.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=patmans@us.ibm.com \
--cc=torvalds@transmeta.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.