From: David Wysochanski <davidw@netapp.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Brian King <brking@us.ibm.com>,
James Bottomley <James.Bottomley@SteelEye.com>,
SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] Recognize missing LUNs for non-standard devices
Date: Tue, 07 Feb 2006 15:44:38 -0500 [thread overview]
Message-ID: <43E906B6.3000903@netapp.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0602071027340.5164-100000@iolanthe.rowland.org>
Alan Stern wrote:
> On Tue, 7 Feb 2006, Brian King wrote:
>
> > > I was afraid that might happen. Okay, forget the patch.
> > >
> > > How come you didn't mention the ipr driver before when I first raised the
> > > possibility of making this change?
> >
> > Sorry about that... I wanted to verify on my end that the scsi level getting
> > returned was 0 before doing so. Your repost was a reminder...
>
> Maybe there's a way around this. Would it be okay to add a flag to the
> target structure, to indicate that PDT = 0x1f should be interpreted as "No
> LUN present"?
>
> Alan Stern
>
I have this same problem for netapp targets (different scsi_level)
and have been meaning to submit a patch so I'm interested in any
patch you might have.
next prev parent reply other threads:[~2006-02-07 20:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 21:59 [PATCH] Recognize missing LUNs for non-standard devices Alan Stern
2006-02-06 22:55 ` Brian King
2006-02-07 14:53 ` Alan Stern
2006-02-07 15:16 ` Brian King
2006-02-07 15:29 ` Alan Stern
2006-02-07 15:40 ` Brian King
2006-02-09 20:26 ` Alan Stern
2006-02-07 20:44 ` David Wysochanski [this message]
2006-02-07 21:22 ` Alan Stern
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=43E906B6.3000903@netapp.com \
--to=davidw@netapp.com \
--cc=James.Bottomley@SteelEye.com \
--cc=brking@us.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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.