From: Douglas Gilbert <dougg@torque.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] include/scsi/scsi.h replace u8 in 2.5.69
Date: Wed, 14 May 2003 23:10:27 +1000 [thread overview]
Message-ID: <3EC24043.6070109@torque.net> (raw)
In-Reply-To: <20030514090218.A7371@infradead.org>
Christoph Hellwig wrote:
> On Wed, May 14, 2003 at 04:39:43PM +1000, Douglas Gilbert wrote:
>
>>Here is a simple patch to replace the single occurrence
>>of "u8" with "u_char" in include/scsi/scsi.h .
>
>
> That's wrong. No userland should include kernwel headers.
> (and u_char is a non-standard type, too).
Christoph,
That's naive. In some case glibc's headers and libraries
(e.g. mknod) are an impediment to development.
If I add one define to ~linux/include/scsi/sg.h just
how long do you think it takes for it to appear in
/usr/include/scsi/sg.h?
It can take over a year in my experience.
Put another way, the sg.h header that applications use
should match the sg driver in the kernel not the glibc
version. The glibc maintainers add nothing to the
interface (apart from inertia and some bugs once in a
while).
Applications that include sg.h typically include scsi.h
as well. Only when I change sg.h does this problem arise.
It is one thing to state a policy (e.g. "no user program
should include kernel headers") it is another thing to
gratuitously break those few programs that have good
reason not to follow that policy.
Doug Gilbert
next prev parent reply other threads:[~2003-05-14 12:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 6:39 [PATCH] include/scsi/scsi.h replace u8 in 2.5.69 Douglas Gilbert
2003-05-14 8:02 ` Christoph Hellwig
2003-05-14 13:05 ` Jeff Garzik
2003-05-14 13:10 ` Douglas Gilbert [this message]
2003-05-14 13:14 ` Christoph Hellwig
2003-05-14 13:54 ` Andries Brouwer
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=3EC24043.6070109@torque.net \
--to=dougg@torque.net \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
/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