From: Boaz Harrosh <bharrosh@panasas.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scsi: consistent use of __u8 in scsi/scsi.h
Date: Wed, 29 Jul 2009 17:09:53 +0300 [thread overview]
Message-ID: <4A705831.3010002@panasas.com> (raw)
In-Reply-To: <1248875763.3900.1.camel@mulgrave.site>
On 07/29/2009 04:56 PM, James Bottomley wrote:
> On Wed, 2009-07-29 at 14:11 +0300, Michael S. Tsirkin wrote:
>> scsi/scsi.h is exported to userspace, so it should
>> use __u8 instead of u8 as other userspace-visible headers do.
>
> Actually, can we just put a hold on this until we decide what we're
> doing with exporting include/scsi.
>
> Arguments so far are
>
> 1. Don't export and let glibc supply the headers (as it does now)
> 2. Move headers to be exported to include/linux
> 3. Take over include/scsi export from glibc: this will necessitate
> comparing our current headers and those of glibc and moving
> stuff around.
>
I'm all for 3. I think if done we should do it for all include/scsi at once.
No need for prolonged pain.
[]$ ls /usr/include/scsi
scsi.h
scsi_ioctl.h
scsi_tgt_if.h
sg.h
However I'll have to ask my employers if they can spare me, so any other
volunteers?
TODO:
* Fix up Kernel headers by complying to check_headers
* Test drive some example user-mode applications including glibc itself.
* send patches to glibc
* send patches to Kernel
* Notify distributions.
> James
>
Boaz
next prev parent reply other threads:[~2009-07-29 14:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 11:11 [PATCH] scsi: consistent use of __u8 in scsi/scsi.h Michael S. Tsirkin
2009-07-29 11:11 ` Michael S. Tsirkin
2009-07-29 13:56 ` James Bottomley
2009-07-29 14:09 ` Boaz Harrosh [this message]
2009-07-29 20:56 ` Michael S. Tsirkin
2009-07-30 9:05 ` Boaz Harrosh
2009-07-30 9:45 ` Michael S. Tsirkin
2009-07-30 9:36 ` Michael S. Tsirkin
2009-07-30 13:16 ` Boaz Harrosh
2009-07-29 16:28 ` Sam Ravnborg
2009-07-29 16:37 ` James Bottomley
2009-07-29 19:29 ` Sam Ravnborg
2009-07-30 9:23 ` Boaz Harrosh
2009-07-30 9:34 ` Michael S. Tsirkin
2009-07-30 10:40 ` Sam Ravnborg
2009-07-29 21:11 ` Michael S. Tsirkin
2009-08-16 13:42 ` Michael S. Tsirkin
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=4A705831.3010002@panasas.com \
--to=bharrosh@panasas.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mst@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.