From: Tom Coughlan <coughlan@redhat.com>
To: sullivan@austin.ibm.com, linux-scsi@vger.kernel.org
Subject: Re: [PATCH][RFC] Driverfs support for SCSI devices (updated)
Date: Wed, 19 Jun 2002 10:13:58 -0400 [thread overview]
Message-ID: <3D1091A6.D6E5A9EB@redhat.com> (raw)
Hello Mike,
Just one point on your scanning of Inquiry page 83. As you know,
the page may contain many Identifiers. Each Identifier has an
Association field. This field indicates whether the Identifier is
associated with the logical unit, or with a port that is used to
access the logical unit. You should only use an identifier that is
associated with the logical unit.
I don't think may vendors are putting port identifiers in Page 83,
so this may not be a big deal, but I'm worried that if they do, the
FC port IDs will show up as Type 3 Identifiers, and we will
incorrectly select a port ID instead of the Logical Unit ID.
Thanks.
--
Tom Coughlan
Red Hat
978-692-3113 ext. 23209
next reply other threads:[~2002-06-19 14:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-19 14:13 Tom Coughlan [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-17 23:16 [PATCH][RFC] Driverfs support for SCSI devices James Bottomley
2002-06-18 21:56 ` [PATCH][RFC] Driverfs support for SCSI devices (updated) sullivan
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=3D1091A6.D6E5A9EB@redhat.com \
--to=coughlan@redhat.com \
--cc=linux-scsi@vger.kernel.org \
--cc=sullivan@austin.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