public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Hannes Reinecke <hare@suse.de>
Cc: sekharan@us.ibm.com, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] Add 'tpgs' sysfs attribute for SCSI devices
Date: Wed, 18 Mar 2009 13:58:55 +0000	[thread overview]
Message-ID: <1237384735.3350.0.camel@localhost.localdomain> (raw)
In-Reply-To: <20090318120206.0BB1418C79D@pentland.suse.de>

On Wed, 2009-03-18 at 13:02 +0100, Hannes Reinecke wrote:
> We need to export the 'TGPS' setting of the
> inquiry data to properly support ALUA.
> 
> Signed-off-by: Hannes Reinecke <hare@suse.de>
> ---
>  drivers/scsi/scsi_scan.c   |    1 +
>  drivers/scsi/scsi_sysfs.c  |    2 ++
>  include/scsi/scsi_device.h |    3 ++-
>  3 files changed, 5 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/scsi/scsi_scan.c b/drivers/scsi/scsi_scan.c
> index a14d245..d1619ed 100644
> --- a/drivers/scsi/scsi_scan.c
> +++ b/drivers/scsi/scsi_scan.c
> @@ -836,6 +836,7 @@ static int scsi_add_lun(struct scsi_device *sdev, unsigned char *inq_result,
>  	sdev->inq_periph_qual = (inq_result[0] >> 5) & 7;
>  	sdev->lockable = sdev->removable;
>  	sdev->soft_reset = (inq_result[7] & 1) && ((inq_result[3] & 7) == 2);
> +	sdev->tpgs = (inq_result[5] >> 4) & 3;

As far as I can tell, this is a read only parameter, isn't it?

In that case, why not just do what we do for the SPI inquiry data and
have a wrapper pulling it out of sdev->inquiry instead of a new flag in
sdev?

James



  reply	other threads:[~2009-03-18 13:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-18 12:02 [PATCH] Add 'tpgs' sysfs attribute for SCSI devices Hannes Reinecke
2009-03-18 13:58 ` James Bottomley [this message]
2009-03-18 14:02   ` Hannes Reinecke
2009-03-18 14:09     ` James Bottomley

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=1237384735.3350.0.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=hare@suse.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=sekharan@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox