From: Christoph Hellwig <hch@lst.de>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Andy Grover <agrover@redhat.com>, linux-scsi@vger.kernel.org, hch@lst.de
Subject: Re: [PATCH 3/3] scsi: Remove scsi_ioctl.h
Date: Fri, 9 Jan 2015 10:05:02 +0100 [thread overview]
Message-ID: <20150109090502.GA21959@lst.de> (raw)
In-Reply-To: <1420749302.5830.31.camel@HansenPartnership.com>
On Thu, Jan 08, 2015 at 12:35:02PM -0800, James Bottomley wrote:
> What's the transition plan for userspace? If you look at glibc
> currently, it supplies both scsi.h and scsi_ioctl.h. If we're
> persuading the glibc folks to go with our versions from uapi, I think
> removing a file which is an effective compile breaker for userspace is a
> really bad idea. Duplicating scsi_ioctl.h definitions in scsi.h would
> also cause them problems.
I thought about this a whіle ago, and I think reusing scsi/*.h is a bad
idea exactly because glibc provides old versions of these.
I'd suggest adding a linux/uapi/scsi_ioctl.h instead.
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-01-09 9:05 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
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 [this message]
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=20150109090502.GA21959@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).