From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Christof Schmitt <christof.schmitt@de.ibm.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [RFC] Set functions for scsi_cmnd result
Date: Thu, 12 Jun 2008 10:55:41 -0500 [thread overview]
Message-ID: <1213286142.3426.26.camel@localhost.localdomain> (raw)
In-Reply-To: <20080612092955.GA9032@schmichrtp.de.ibm.com>
On Thu, 2008-06-12 at 11:29 +0200, Christof Schmitt wrote:
> zfcp currently has helper functions to set the host and driver bytes
> in the scsi_cmnd result. These functions do not belong in the
> low-level driver. The attached patch moves the functions to the global
> SCSI header file, so that every driver can use them.
>
> If nobody wants ths, i will remove them from zfcp and directly
> manipulate the status like other drivers do.
>
> ---
> drivers/s390/scsi/zfcp_scsi.c | 20 --------------------
> include/scsi/scsi.h | 10 ++++++++++
> 2 files changed, 10 insertions(+), 20 deletions(-)
>
> --- a/drivers/s390/scsi/zfcp_scsi.c 2008-06-12 11:00:16.000000000 +0200
> +++ b/drivers/s390/scsi/zfcp_scsi.c 2008-06-12 11:06:37.000000000 +0200
> @@ -107,27 +107,7 @@ zfcp_set_fcp_dl(struct fcp_cmnd_iu *fcp_
> *zfcp_get_fcp_dl_ptr(fcp_cmd) = fcp_dl;
> }
>
> -/*
> - * note: it's a bit-or operation not an assignment
> - * regarding the specified byte
> - */
> -static inline void
> -set_byte(int *result, char status, char pos)
> -{
> - *result |= status << (pos * 8);
> -}
>
> -void
> -set_host_byte(int *result, char status)
> -{
> - set_byte(result, status, 2);
> -}
> -
> -void
> -set_driver_byte(int *result, char status)
> -{
> - set_byte(result, status, 3);
> -}
>
> static int
> zfcp_scsi_slave_alloc(struct scsi_device *sdp)
> --- a/include/scsi/scsi.h 2008-06-10 17:30:49.000000000 +0200
> +++ b/include/scsi/scsi.h 2008-06-12 11:06:34.000000000 +0200
> @@ -425,6 +425,16 @@ struct scsi_lun {
> #define driver_byte(result) (((result) >> 24) & 0xff)
> #define suggestion(result) (driver_byte(result) & SUGGEST_MASK)
>
> +static inline void set_host_byte(int *result, char status)
> +{
> + *result |= status << 16;
> +}
> +
> +static inline void set_driver_byte(int *result, char status)
> +{
> + *result |= status << 24;
> +}
> +
If we're making accessors, it might be better if they took a struct
scsi_cmnd rather than a pointer to one of its elements. Other than
that, this looks fine.
James
next prev parent reply other threads:[~2008-06-12 15:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 9:29 [RFC] Set functions for scsi_cmnd result Christof Schmitt
2008-06-12 15:55 ` James Bottomley [this message]
2008-06-16 8:58 ` Christof Schmitt
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=1213286142.3426.26.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=christof.schmitt@de.ibm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox