From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Jaswinder Singh Rajput <jaswinder@kernel.org>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Boaz Harrosh <bharrosh@panasas.com>,
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: Sat, 27 Jun 2009 12:27:08 -0500 [thread overview]
Message-ID: <1246123628.3990.19.camel@mulgrave.site> (raw)
In-Reply-To: <1246122359.32198.7.camel@hpdv5.satnam>
All SCSI patches should be cc'd to the SCSI list
On Sat, 2009-06-27 at 22:35 +0530, Jaswinder Singh Rajput wrote:
> userspace cannot use scsi_command_size_tbl, COMMAND_SIZE
> and scsi_device_type defined in kernel
>
> fix the following 'make headers_check' warnings:
>
> usr/include/scsi/scsi.h:159: userspace cannot call function or variable defined in the kernel
> usr/include/scsi/scsi.h:285: userspace cannot call function or variable defined in the kernel
>
> Signed-off-by: Jaswinder Singh Rajput <jaswinderrajput@gmail.com>
> ---
> include/scsi/scsi.h | 13 +++++++------
> 1 files changed, 7 insertions(+), 6 deletions(-)
>
> diff --git a/include/scsi/scsi.h b/include/scsi/scsi.h
> index 084478e..7ba5acf 100644
> --- a/include/scsi/scsi.h
> +++ b/include/scsi/scsi.h
> @@ -156,9 +156,6 @@ scsi_varlen_cdb_length(const void *hdr)
> return ((struct scsi_varlen_cdb_hdr *)hdr)->additional_cdb_length + 8;
> }
>
> -extern const unsigned char scsi_command_size_tbl[8];
> -#define COMMAND_SIZE(opcode) scsi_command_size_tbl[((opcode) >> 5) & 7]
> -
> static inline unsigned
> scsi_command_size(const unsigned char *cmnd)
> {
> @@ -166,6 +163,13 @@ scsi_command_size(const unsigned char *cmnd)
> scsi_varlen_cdb_length(cmnd) : COMMAND_SIZE(cmnd[0]);
Even a simple eyeball inspection of this patch shows that the removal of
COMMAND_SIZE above causes this inline function to fail to compile.
If you can't be bothered even to read your own patches or at the very
least compile test them, what makes you think I should bother reading
anything you send in?
James
next prev parent reply other threads:[~2009-06-27 17:27 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 [this message]
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
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=1246123628.3990.19.camel@mulgrave.site \
--to=james.bottomley@hansenpartnership.com \
--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=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®