* RFC: Add I/O class enum values to <scsi/srp.h>
@ 2006-06-05 19:17 Roland Dreier
2006-06-05 19:40 ` James Bottomley
0 siblings, 1 reply; 3+ messages in thread
From: Roland Dreier @ 2006-06-05 19:17 UTC (permalink / raw)
To: linux-scsi, James.Bottomley; +Cc: openib-general
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;
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: RFC: Add I/O class enum values to <scsi/srp.h>
2006-06-05 19:17 RFC: Add I/O class enum values to <scsi/srp.h> Roland Dreier
@ 2006-06-05 19:40 ` James Bottomley
2006-06-05 19:55 ` Roland Dreier
0 siblings, 1 reply; 3+ messages in thread
From: James Bottomley @ 2006-06-05 19:40 UTC (permalink / raw)
To: Roland Dreier; +Cc: linux-scsi, openib-general
On Mon, 2006-06-05 at 12:17 -0700, Roland Dreier wrote:
> 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.
No objection here ... but if you do, it will entangle our git trees even
more nastily, since the srp.h file is created in the scsi-misc-2.6 tree.
James
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: RFC: Add I/O class enum values to <scsi/srp.h>
2006-06-05 19:40 ` James Bottomley
@ 2006-06-05 19:55 ` Roland Dreier
0 siblings, 0 replies; 3+ messages in thread
From: Roland Dreier @ 2006-06-05 19:55 UTC (permalink / raw)
To: James Bottomley; +Cc: linux-scsi, openib-general
James> No objection here ... but if you do, it will entangle our
James> git trees even more nastily, since the srp.h file is
James> created in the scsi-misc-2.6 tree.
No, I think we're OK. srp.h is already in Linus's tree (it went in as
part of the original IB SRP initiator merge), and scsi-misc doesn't have
any changes after ec448a0a36 (which is already upstream) in it. So
putting the IO Class change in my tree actually reduces the dependency
between our trees, since I can put the IB SRP changes in my tree
without worrying about you merging the srp.h change first.
- R.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2006-06-05 19:55 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-06-05 19:17 RFC: Add I/O class enum values to <scsi/srp.h> Roland Dreier
2006-06-05 19:40 ` James Bottomley
2006-06-05 19:55 ` Roland Dreier
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).