From: Jens Axboe <axboe@suse.de>
To: Joerg Schilling <schilling@fokus.fraunhofer.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel includefile bug not fixed after a year :-(
Date: Tue, 30 Sep 2003 13:05:16 +0200 [thread overview]
Message-ID: <20030930110516.GK2908@suse.de> (raw)
In-Reply-To: <200309301028.h8UASdTI004280@burner.fokus.fraunhofer.de>
On Tue, Sep 30 2003, Joerg Schilling wrote:
> A year after I did report this inconsistency, it is still not fixed
>
> If include/scsi/scsi.h is included without __KERNEL__ #defined, then this
> error message apears.
>
> /usr/src/linux/include/scsi/scsi.h:172: parse error before "u8"
> /usr/src/linux/include/scsi/scsi.h:172: warning: no semicolon at end of struct
> or union
> /usr/src/linux/include/scsi/scsi.h:173: warning: data definition has no type or
> storage class
>
> Is there no interest in user applications for kernel features or is there just
> no kernel maintainer left over who makes the needed work?
/usr/include/scsi/scsi.h looks fine on my system, probably also on
yours. You should not include kernel headers in your user space program.
--
Jens Axboe
next prev parent reply other threads:[~2003-09-30 11:05 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-30 10:28 Kernel includefile bug not fixed after a year :-( Joerg Schilling
2003-09-30 11:05 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-30 11:44 Joerg Schilling
2003-09-30 11:54 ` Jens Axboe
2003-09-30 12:12 ` Andreas Steinmetz
2003-09-30 12:21 ` Jens Axboe
2003-09-30 12:26 ` Andreas Steinmetz
2003-09-30 12:30 ` Jens Axboe
2003-09-30 12:32 ` David S. Miller
2003-09-30 12:40 ` Jens Axboe
2003-09-30 12:39 ` David S. Miller
2003-09-30 12:23 ` David S. Miller
2003-09-30 12:28 ` Jens Axboe
2003-09-30 12:34 ` David S. Miller
2003-09-30 12:42 ` Jens Axboe
2003-09-30 19:09 ` Erik Andersen
2003-10-01 8:48 ` Paul Rolland
2003-10-01 8:55 ` Arjan van de Ven
2003-10-01 17:49 ` Erik Andersen
2003-09-30 16:10 ` Sam Ravnborg
2003-10-01 6:39 ` David S. Miller
2003-10-02 6:42 ` Eric W. Biederman
2003-09-30 19:04 ` Erik Andersen
2003-09-30 12:25 ` Nick Piggin
2003-09-30 19:00 ` Erik Andersen
2003-10-01 8:47 ` Paul Rolland
2003-09-30 11:57 Joerg Schilling
2003-09-30 12:06 ` Jens Axboe
2003-09-30 12:28 ` David S. Miller
2003-09-30 12:38 ` Jens Axboe
2003-09-30 14:41 ` Krzysztof Halasa
2003-10-10 6:36 ` Sandy Harris
2003-09-30 12:37 Joerg Schilling
2003-09-30 13:21 ` Tomas Szepe
2003-09-30 12:52 Joerg Schilling
2003-09-30 13:26 Joerg Schilling
2003-10-01 1:05 Albert Cahalan
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=20030930110516.GK2908@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=schilling@fokus.fraunhofer.de \
/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