From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Sam Ravnborg <sam@ravnborg.org>
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 16:37:36 +0000 [thread overview]
Message-ID: <1248885456.3900.48.camel@mulgrave.site> (raw)
In-Reply-To: <20090729162844.GA22561@merkur.ravnborg.org>
On Wed, 2009-07-29 at 18:28 +0200, Sam Ravnborg wrote:
> On Wed, Jul 29, 2009 at 08:56:03AM -0500, 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.
>
> 2 + 3...
> Let include/scsi be kernel internal stuff.
> And have the exported headers in include/linux.
I don't quite understand what you're saying here. I think 2 and 3 are
either/or options. Either we move the exported files to include/linux
or we export from include/scsi.
I have to say I don't like option 2 because the breakage is visible to
user level programs (unless we can persuade glibc people to #include
<linux/scsi.h> in scsi/scsi.h).
> This is how net/ handle their headers.
>
> I did a quick diff of the glibc provided scsi.h and kernel scsi.h.
> >From a quick look it seems that we have more in the kernel version
> than the glibc version - and no obvious conflicts.
>
> But agree with Boaz that we should do this in one go.
James
next prev parent reply other threads:[~2009-07-29 16:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 11:11 Michael S. Tsirkin
2009-07-29 13:56 ` James Bottomley
2009-07-29 14:09 ` Boaz Harrosh
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 [this message]
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=1248885456.3900.48.camel@mulgrave.site \
--to=james.bottomley@hansenpartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mst@redhat.com \
--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®