public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Christie <michaelc@cs.wisc.edu>
To: Patrick Mansfield <patmans@us.ibm.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: scsi scan bug when peripheral qualifier of 3 is returned
Date: Thu, 05 Jan 2006 10:56:52 -0600	[thread overview]
Message-ID: <43BD4FD4.8020806@cs.wisc.edu> (raw)
In-Reply-To: <20060104222522.GA5741@us.ibm.com>

Patrick Mansfield wrote:
> Then like this?

Yep, this works for our setup. Thanks.

> 
> --- linux-2.6.15/drivers/scsi/orig-scsi_scan.c	2006-01-02 21:52:12.000000000 -0800
> +++ linux-2.6.15/drivers/scsi/scsi_scan.c	2006-01-04 13:03:27.000000000 -0800
> @@ -868,6 +868,8 @@ static int scsi_probe_and_add_lun(struct
>  
>  	if (scsi_probe_lun(sdev, result, result_len, &bflags))
>  		goto out_free_result;
> +	if (bflagsp)
> +		*bflagsp = bflags;
>  
>  	/*
>  	 * result contains valid SCSI INQUIRY data.
> @@ -896,8 +898,6 @@ static int scsi_probe_and_add_lun(struct
>  			sdev->lockable = 0;
>  			scsi_unlock_floptical(sdev, result);
>  		}
> -		if (bflagsp)
> -			*bflagsp = bflags;
>  	}
>  
>   out_free_result:
> 

.....

> 
> Don't forget you can dynamically add devinfo values via modparam and
> /proc/scsi.
> 

I did not know this. I was looking for a writable proc file for some 
reason. Thanks.

      reply	other threads:[~2006-01-05 16:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-04  7:11 scsi scan bug when peripheral qualifier of 3 is returned Mike Christie
2006-01-04 17:40 ` Patrick Mansfield
2006-01-04 18:28   ` Mike Christie
2006-01-04 19:01     ` Patrick Mansfield
2006-01-04 20:31       ` Mike Christie
2006-01-04 22:25         ` Patrick Mansfield
2006-01-05 16:56           ` Mike Christie [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=43BD4FD4.8020806@cs.wisc.edu \
    --to=michaelc@cs.wisc.edu \
    --cc=linux-scsi@vger.kernel.org \
    --cc=patmans@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