From: Christoph Hellwig <hch@lst.de>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Andy Grover <agrover@redhat.com>, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 2/3] scsi: Move user-shareable stuff in scsi/scsi.h to uapi/scsi/scsi.h
Date: Fri, 9 Jan 2015 18:11:48 +0100 [thread overview]
Message-ID: <20150109171148.GA17380@lst.de> (raw)
In-Reply-To: <1420821180.2064.10.camel@HansenPartnership.com>
On Fri, Jan 09, 2015 at 08:33:00AM -0800, James Bottomley wrote:
> Yes, but they have to be delivered to users somehow. If you look at
> debian, they deliver the headers through the linux-dev-libc package
> which installs into the /usr/include directory.
linux-libc-dev despite the name is provided from the kernel source package:
https://packages.debian.org/sid/linux-libc-dev
> Since glibc currently
> owns the entirety of /usr/include/scsi, we have to help the distros
> figure out how we deliver the headers, otherwise all uapi exports of
> SCSI stuff just gets ignored ...
That's why I've been arguing for adding a new linux/scsi_ioctl.h header
to bypass that whole conflict since my first mail in this thread.
next prev parent reply other threads:[~2015-01-09 17:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 19:47 [PATCH 0/3] Add uapi/scsi/scsi.h Andy Grover
2015-01-08 19:47 ` [PATCH 1/3] scsi: add WRITE_VERIFY_16 to scsi.h Andy Grover
2015-01-08 19:47 ` [PATCH 2/3] scsi: Move user-shareable stuff in scsi/scsi.h to uapi/scsi/scsi.h Andy Grover
2015-01-09 10:14 ` Christoph Hellwig
2015-01-09 15:27 ` James Bottomley
2015-01-09 15:46 ` Christoph Hellwig
2015-01-09 15:50 ` James Bottomley
2015-01-09 16:01 ` Christoph Hellwig
2015-01-09 16:33 ` James Bottomley
2015-01-09 17:11 ` Christoph Hellwig [this message]
2015-01-09 17:44 ` James Bottomley
2015-01-08 19:47 ` [PATCH 3/3] scsi: Remove scsi_ioctl.h Andy Grover
2015-01-08 20:35 ` James Bottomley
2015-01-08 21:26 ` Andy Grover
2015-01-09 9:05 ` Christoph Hellwig
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=20150109171148.GA17380@lst.de \
--to=hch@lst.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=agrover@redhat.com \
--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).