From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: James Smart <James.Smart@Emulex.Com>
Cc: Boaz Harrosh <bharrosh@panasas.com>,
Jaswinder Singh Rajput <jaswinder@kernel.org>,
Olaf Hering <olh@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
Sam Ravnborg <sam@ravnborg.org>,
Benny Halevy <bhalevy@panasas.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] SCSI: userspace cannot use scsi_command_size_tbl, COMMAND_SIZE and scsi_device_type
Date: Sun, 28 Jun 2009 09:44:42 -0500 [thread overview]
Message-ID: <1246200282.4190.13.camel@mulgrave.site> (raw)
In-Reply-To: <4A477F00.70305@emulex.com>
On Sun, 2009-06-28 at 10:32 -0400, James Smart wrote:
> Sorry folks -- the nuance of the clibrary having it's own version of a
> kernel header for distros was completely unknown to me.
>
> Christoph mentioned this to me last week, with the recommendation to
> back out the patch and move the other headers that were exprted into
> include/linux - thus nothing in include/scsi gets export. No Problem.
> and I'll do so shortly.
Actually, I'm not sure that's the best way forwards ... the idea of
include/scsi is to group all the SCSI headers together; having to put
them in include/linux if they need to be exported defeats that purpose
slightly.
I think the first point of business might be to find out why (or even
if) glibc still wants its own SCSI headers. After all, we now have
quite an anomaly: if you use the old SG_IO ioctl, glibc supplies the
header in include/scsi/sg.h; if you use the new bsg SG_IO then we supply
it in include/linux/bsg.h
> How does a lowly contributor track these kind of nuances ?
If the creator of the kernel header exports missed this problem for a
year, I think it's safe to assume you don't lose brownie points for not
spotting it either.
James
next prev parent reply other threads:[~2009-06-28 14:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-27 17:05 Jaswinder Singh Rajput
2009-06-27 17:27 ` James Bottomley
2009-06-27 17:56 ` Jaswinder Singh Rajput
2009-06-27 18:28 ` Matthew Wilcox
2009-06-27 18:40 ` Jaswinder Singh Rajput
2009-06-28 13:52 ` James Bottomley
2009-06-28 14:09 ` Boaz Harrosh
2009-07-02 14:41 ` Jaswinder Singh Rajput
2009-06-28 7:56 ` Boaz Harrosh
2009-06-28 14:32 ` James Smart
2009-06-28 14:44 ` James Bottomley [this message]
2009-06-28 16:00 ` Boaz Harrosh
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=1246200282.4190.13.camel@mulgrave.site \
--to=james.bottomley@hansenpartnership.com \
--cc=James.Smart@Emulex.Com \
--cc=akpm@linux-foundation.org \
--cc=bhalevy@panasas.com \
--cc=bharrosh@panasas.com \
--cc=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=olh@suse.de \
--cc=sam@ravnborg.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
all inboxes | Powered by JetHome®