Message ID | 1dcadbce-8a97-9578-686a-c43bd8dc06fc@kernel.dk (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
On Thu, Nov 23, 2017 at 10:04:55PM -0700, Jens Axboe wrote: > > + NVME_FC_Q_LIVE = (1 << 1), > > }; > > > > for flags that are used with set_bit() and friends? That's just > > misleading, should be 0, 1, etc, not a shift. > > > > The rest looks pretty straight forward, but the above is an eye sore. Yes, it is misleading, but so far harmless. Your fixup looks good to me: Reviewed-by: Christoph Hellwig <hch@lst.de>
On 11/24/2017 01:32 AM, Christoph Hellwig wrote: > On Thu, Nov 23, 2017 at 10:04:55PM -0700, Jens Axboe wrote: >>> + NVME_FC_Q_LIVE = (1 << 1), >>> }; >>> >>> for flags that are used with set_bit() and friends? That's just >>> misleading, should be 0, 1, etc, not a shift. >>> >>> The rest looks pretty straight forward, but the above is an eye sore. > > Yes, it is misleading, but so far harmless. Yeah, but it just takes a few more bits... > Your fixup looks good to me: > > Reviewed-by: Christoph Hellwig <hch@lst.de> Thanks, I've added it.
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 */