From: Christoph Hellwig <hch@infradead.org>
To: Douglas Gilbert <dougg@torque.net>
Cc: Christoph Hellwig <hch@infradead.org>, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] include/scsi/scsi.h replace u8 in 2.5.69
Date: Wed, 14 May 2003 14:14:55 +0100 [thread overview]
Message-ID: <20030514141455.A20912@infradead.org> (raw)
In-Reply-To: <3EC24043.6070109@torque.net>; from dougg@torque.net on Wed, May 14, 2003 at 11:10:27PM +1000
On Wed, May 14, 2003 at 11:10:27PM +1000, Douglas Gilbert wrote:
> 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?
As long as it takes you to send the same diff to Ullrich.
> 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
What kernel? I run everything from 2.2.2x + local hacks to latest
2.5 on one box.
> 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.
So get declarations for u8 into your program. It's a kernel
header for a reason and if you ignore the advise _you_ have
to work around the problems arising from it not the kernel.
next prev parent reply other threads:[~2003-05-14 13:02 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
2003-05-14 13:14 ` Christoph Hellwig [this message]
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=20030514141455.A20912@infradead.org \
--to=hch@infradead.org \
--cc=dougg@torque.net \
--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