Re: [PATCH 2/3] nvme-loop: use blk_mq_hctx_set_fq_lock_class to set loop's lock class

To: Ming Lei <ming.lei@xxxxxxxxxx>
Subject: Re: [PATCH 2/3] nvme-loop: use blk_mq_hctx_set_fq_lock_class to set loop's lock class
From: Christoph Hellwig <hch@xxxxxx>
Date: Mon, 16 Nov 2020 18:27:12 +0100
Cc: Jens Axboe <axboe@xxxxxxxxx>, linux-block@xxxxxxxxxxxxxxx, linux-nvme@xxxxxxxxxxxxxxxxxxx, Christoph Hellwig <hch@xxxxxx>, Qian Cai <cai@xxxxxxxxxx>, Sumit Saxena <sumit.saxena@xxxxxxxxxxxx>, John Garry <john.garry@xxxxxxxxxx>, Kashyap Desai <kashyap.desai@xxxxxxxxxxxx>, Bart Van Assche <bvanassche@xxxxxxx>, Hannes Reinecke <hare@xxxxxxx>
In-reply-to: <20201112075526.947079-3-ming.lei@redhat.com>
References: <20201112075526.947079-1-ming.lei@redhat.com> <20201112075526.947079-3-ming.lei@redhat.com>
User-agent: Mutt/1.5.17 (2007-11-01)

Looks good,

Reviewed-by: Christoph Hellwig <hch@xxxxxx>

References:
- [PATCH 0/3] blk-mq/nvme-loop: use nvme-loop's lock class for addressing lockdep false positive warning
  - From: Ming Lei
- [PATCH 2/3] nvme-loop: use blk_mq_hctx_set_fq_lock_class to set loop's lock class
  - From: Ming Lei