summaryrefslogtreecommitdiffstats
path: root/block
diff options
context:
space:
mode:
authorDan Carpenter <dan.carpenter@oracle.com>2018-06-07 11:27:41 +0300
committerJens Axboe <axboe@kernel.dk>2018-06-08 12:51:11 -0600
commit77016199f11eacd7b23e2faeb4d0f36166e3530b (patch)
treef057546cbab3803e4469af86bebfb6aa0fbf4ca2 /block
parent69f4eb9ff79556c1a3daf5af5573594c196f30cc (diff)
downloadlinux-77016199f11eacd7b23e2faeb4d0f36166e3530b.tar.bz2
nvme: cleanup double shift issue
The problem here is that set_bit() and test_bit() take a bit number so we should be passing 0 but instead we're passing (1 << 0) which leads to a double shift. It doesn't cause a runtime bug in the current code because it's done consistently and we only set that one bit. I decided to just re-use NVME_AER_NOTICE_NS_CHANGED instead of introducing a new define for this. Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com> Reviewed-by: Sagi Grimberg <sagi@grimberg.me> Signed-off-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'block')
0 files changed, 0 insertions, 0 deletions