summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJens Axboe <axboe@kernel.dk>2017-11-24 10:12:33 -0700
committerJens Axboe <axboe@kernel.dk>2017-11-24 10:12:33 -0700
commit26c0a26d78bc7c2943d55121a32cb85a4594f8ea (patch)
tree9dd79dc9b566bef99dba547d8913854853c354a0
parent3dfbdc44d69b2cd7e382fd084a5c860d2cea24f6 (diff)
downloadlinux-stable-26c0a26d78bc7c2943d55121a32cb85a4594f8ea.tar.gz
linux-stable-26c0a26d78bc7c2943d55121a32cb85a4594f8ea.tar.bz2
linux-stable-26c0a26d78bc7c2943d55121a32cb85a4594f8ea.zip
nvme-fc: don't use bit masks for set/test_bit() numbers
So far harmless, but it's confusing and a bug waiting to happen if the shifts grow larger than 4. Reviewed-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Jens Axboe <axboe@kernel.dk>
-rw-r--r--drivers/nvme/host/fc.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/drivers/nvme/host/fc.c b/drivers/nvme/host/fc.c
index e0577bf33f45..0a8af4daef89 100644
--- a/drivers/nvme/host/fc.c
+++ b/drivers/nvme/host/fc.c
@@ -31,8 +31,8 @@
enum nvme_fc_queue_flags {
- NVME_FC_Q_CONNECTED = (1 << 0),
- NVME_FC_Q_LIVE = (1 << 1),
+ NVME_FC_Q_CONNECTED = 0,
+ NVME_FC_Q_LIVE,
};
#define NVMEFC_QUEUE_DELAY 3 /* ms units */