From: Olaf Hering <olh@suse.de>
To: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
libc-alpha@sources.redhat.com
Subject: glibc and make headers_install_all provide /usr/include/scsi
Date: Mon, 6 Aug 2007 14:45:46 +0200 [thread overview]
Message-ID: <20070806124546.GA2117@suse.de> (raw)
glibc and make headers_install_all provide /usr/include/scsi
One of them has to go.
A quick diff shows no differences, expect:
scsi.h:
glibc #define STATUS_MASK 0x3e
Linux #define STATUS_MASK 0xfe
glibc #define ABORT 0x06
Linux #define ABORT_TASK_SET 0x06
sg.h:struct sg_iovec ->sg_iovec
unsigned char * in glibc
void * in Linux
glibc #define SG_DEFAULT_RETRIES 1
Linux #define SG_DEFAULT_RETRIES 0
Which copy should be provided by a distributor?
next reply other threads:[~2007-08-06 12:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-06 12:45 Olaf Hering [this message]
2007-08-06 12:52 ` glibc and make headers_install_all provide /usr/include/scsi Christoph Hellwig
2007-08-06 13:02 ` [PATCH] do not export /usr/include/scsi in make headers_install Olaf Hering
2007-08-11 6:42 ` David Woodhouse
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=20070806124546.GA2117@suse.de \
--to=olh@suse.de \
--cc=libc-alpha@sources.redhat.com \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).