From: James Smart <James.Smart@Emulex.Com>
To: linux-scsi@vger.kernel.org
Subject: [PATCH] fc_transport: fix old bug on bitflag definitions
Date: Thu, 20 Nov 2008 10:58:01 -0500 [thread overview]
Message-ID: <1227196681.7483.3.camel@ogier> (raw)
I thought we had corrected this a while ago - however, it's still
in 2.6.28-rc?.
When the fastfail flag was added, it did not account for the flags
being bit fields. Correct the definition so there is no longer a
conflict.
James - we need to get this into 2.6.28
-- james s
Signed-off-by: James Smart <james.smart@emulex.com>
---
scsi_transport_fc.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -upNr a/include/scsi/scsi_transport_fc.h b/include/scsi/scsi_transport_fc.h
--- a/include/scsi/scsi_transport_fc.h 2008-10-18 10:32:54.000000000 -0400
+++ b/include/scsi/scsi_transport_fc.h 2008-11-20 10:54:02.000000000 -0500
@@ -357,7 +357,7 @@ struct fc_rport { /* aka fc_starget_attr
/* bit field values for struct fc_rport "flags" field: */
#define FC_RPORT_DEVLOSS_PENDING 0x01
#define FC_RPORT_SCAN_PENDING 0x02
-#define FC_RPORT_FAST_FAIL_TIMEDOUT 0x03
+#define FC_RPORT_FAST_FAIL_TIMEDOUT 0x04
#define dev_to_rport(d) \
container_of(d, struct fc_rport, dev)
reply other threads:[~2008-11-20 15:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1227196681.7483.3.camel@ogier \
--to=james.smart@emulex.com \
--cc=linux-scsi@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox