From: Jeff Smith <lkml.sepix@code.wastedcycles.net>
To: James Bottomley <James.Bottomley@suse.de>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] SCSI: userspace cannot use scsi_device_type
Date: Wed, 11 Nov 2009 21:22:41 +0000 [thread overview]
Message-ID: <4AFB2B21.4030103@code.wastedcycles.net> (raw)
In-Reply-To: <1257970134.11985.20.camel@mulgrave.site>
James Bottomley wrote:
> On Wed, 2009-11-11 at 18:16 +0000, Jeff Smith wrote:
>> The following patch fixes the 'make headers_check' warning:
>> include/scsi/scsi.h:288: userspace cannot call function or variable defined in the kernel
>> It is similar to a patch from Jaswinder Singh Rajput back in July, which did not initially compile.
[..snip..]
>> A similar patch for the scsi_command_size code should be feasible, but a code search reveals some
[..snip..]
> Actually, there are several other problems like this that need
> fixing ... and for which we have patches submitted.
Thanks for the hint -- I've found some of them now! Sorry! (I am not
on linux-scsi, so I have a bit of catching-up to do.)
> The debating point
> is whether we actually want to clean scsi.h and the allied headers up
> enough so we can ask Ulrich actually to use them for glibc ... and where
> the resulting headers should be placed. So far we have no consensus on
> this.
If there is no agreement on asking Ulrich or on ultimate filestore location, the
question is whether meanwhile it's worth deploying the minimal cleaning necessary
to avoid warnings and other known small difficulties (as mentioned
in eg. Michael S. Tsirkin's patchset). I assume you think that the debate
will resolve itself in due course, so a minor stall now is preferable?
> Personally, I think a line by line comparison of the scsi.h in Ulrich's
> glibc tree and ours making it identical and shoving all the non kernel
> stuff into other headers might be the way to go .. but others have
> disagreed in the past.
Personally I agree with your approach, but I wouldn't want to do actual
work on it if it's unlikely to get deployed.
Jeff
> James
>
>
prev parent reply other threads:[~2009-11-11 21:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 18:16 [PATCH] SCSI: userspace cannot use scsi_device_type Jeff Smith
2009-11-11 20:08 ` James Bottomley
2009-11-11 21:22 ` Jeff Smith [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=4AFB2B21.4030103@code.wastedcycles.net \
--to=lkml.sepix@code.wastedcycles.net \
--cc=James.Bottomley@suse.de \
--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 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.