From: Roland Dreier <rdreier@cisco.com>
To: linux-scsi@vger.kernel.org, James.Bottomley@SteelEye.com
Cc: openib-general@openib.org
Subject: RFC: Add I/O class enum values to <scsi/srp.h>
Date: Mon, 05 Jun 2006 12:17:59 -0700 [thread overview]
Message-ID: <adaodx7o1i0.fsf@cisco.com> (raw)
Does anyone have an objection to me merging the trivial patch below
through my git tree? This will be used by the IB SRP initiator to
work with SilverStorm targets, which still implement rev. 10 of the
SRP spec. I could just make these values private to the IB initiator,
but I figured that things directly from the SRP spec belong in
<scsi/srp.h> rather than in a particular driver's private header.
Thanks,
Roland
diff-tree a13ac0e9f99636a043d197f3349a67303ce4a701 (from bb61dd1fbf59f2291295986bed1f99b48f513fa4)
Author: Ramachandra K <rkuchimanchi@silverstorm.com>
Date: Mon Jun 5 12:13:52 2006 -0700
[SCSI] srp.h: Add I/O Class values
Add enum values for I/O Class values from rev. 10 and rev. 16a SRP
drafts. The values are used to detect targets that implement obsolete
revisions of SRP, so that the initiator can use the old format for
port identifier when connecting to them.
Signed-off-by: Ramachandra K <rkuchimanchi@silverstorm.com>
Signed-off-by: Roland Dreier <rolandd@cisco.com>
diff --git a/include/scsi/srp.h b/include/scsi/srp.h
index 637f77e..ad178fa 100644
--- a/include/scsi/srp.h
+++ b/include/scsi/srp.h
@@ -87,6 +87,11 @@ enum srp_login_rej_reason {
SRP_LOGIN_REJ_CHANNEL_LIMIT_REACHED = 0x00010006
};
+enum {
+ SRP_REV10_IB_IO_CLASS = 0xff00,
+ SRP_REV16A_IB_IO_CLASS = 0x0100
+};
+
struct srp_direct_buf {
__be64 va;
__be32 key;
next reply other threads:[~2006-06-05 19:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-05 19:17 Roland Dreier [this message]
2006-06-05 19:40 ` RFC: Add I/O class enum values to <scsi/srp.h> James Bottomley
2006-06-05 19:55 ` Roland Dreier
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=adaodx7o1i0.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=James.Bottomley@SteelEye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=openib-general@openib.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 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.