From: Christoph Hellwig <hch@infradead.org>
To: Sahara Workshop <workshop@cpt.saharapc.co.za>
Cc: KML <linux-kernel@vger.kernel.org>
Subject: Re: Problems with 2.5.*'s SCSI headers and cdrtools
Date: Fri, 14 Feb 2003 05:58:22 +0000 [thread overview]
Message-ID: <20030214055822.A18415@infradead.org> (raw)
In-Reply-To: <1045201685.5971.78.camel@workshop.saharact.lan>; from workshop@cpt.saharapc.co.za on Fri, Feb 14, 2003 at 07:48:06AM +0200
On Fri, Feb 14, 2003 at 07:48:06AM +0200, Sahara Workshop wrote:
>
> Kernel 2.5.5x (have not tried earlier) and 2.5.60 's scsi/scsi.h do
> not have like in 2.4 the 'include <features.h>', or as it may seem
> to need an 'include <types.h>', and thus cdrtools for one do not
> compile.
>
> The take I get on this from Jorg is that he feels its a problem
> kernel side. Comments ?
The problem is in cdrtools. It should not include kernel headers.
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they
> are addressed. If you have received this email in error please notify
> the system manager. Please note that any views or opinions presented
> in this email are solely those of the author and do not necessarily
> represent those of Sahara Distribution (Pty) Ltd. Finally, while Sahara
> Distribution attempts to ensure that all email is virus-free, Sahara
> Distribution accepts no liability for any damage caused by any virus
> transmitted by this email.
Blah. You sent this mail to a public list so this statement is void.
next prev parent reply other threads:[~2003-02-14 5:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-14 5:48 Sahara Workshop
2003-02-14 5:58 ` Christoph Hellwig [this message]
2003-02-14 6:07 ` Martin Schlemmer
2003-02-14 6:21 ` Christoph Hellwig
2003-02-14 6:27 ` Sahara Workshop
2003-02-14 6:32 ` Christoph Hellwig
2003-02-14 8:48 ` Martin Schlemmer
2003-02-14 6:00 ` Zwane Mwaikambo
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=20030214055822.A18415@infradead.org \
--to=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=workshop@cpt.saharapc.co.za \
/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
all inboxes | Powered by JetHome®