From: Ming Lei <ming.lei@redhat.com>
To: Qian Cai <qcai@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, linux-nvme@lists.infradead.org,
Christoph Hellwig <hch@lst.de>,
Sumit Saxena <sumit.saxena@broadcom.com>,
John Garry <john.garry@huawei.com>,
Kashyap Desai <kashyap.desai@broadcom.com>,
Bart Van Assche <bvanassche@acm.org>,
Hannes Reinecke <hare@suse.de>
Subject: Re: [PATCH 0/3] blk-mq/nvme-loop: use nvme-loop's lock class for addressing lockdep false positive warning
Date: Thu, 3 Dec 2020 08:50:35 +0800 [thread overview]
Message-ID: <20201203005035.GA540033@T590> (raw)
In-Reply-To: <b70f46b855858a28b0e77ee7efbb2dbffbb56490.camel@redhat.com>
On Wed, Dec 02, 2020 at 02:07:08PM -0500, Qian Cai wrote:
> On Mon, 2020-11-30 at 10:36 +0800, Ming Lei wrote:
> > Any chance to take a look? And this issue has been reported several
> > times in RH internal test.
>
> I suppose that you will need to rebase as it does not apply cleanly on today's
> linux-next.
>
I just apply the three patches against for-5.11/block, and they can be
done cleanly.
Thanks,
Ming
WARNING: multiple messages have this Message-ID (diff)
From: Ming Lei <ming.lei@redhat.com>
To: Qian Cai <qcai@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>,
Bart Van Assche <bvanassche@acm.org>,
John Garry <john.garry@huawei.com>,
linux-nvme@lists.infradead.org,
Kashyap Desai <kashyap.desai@broadcom.com>,
linux-block@vger.kernel.org,
Sumit Saxena <sumit.saxena@broadcom.com>,
Hannes Reinecke <hare@suse.de>, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH 0/3] blk-mq/nvme-loop: use nvme-loop's lock class for addressing lockdep false positive warning
Date: Thu, 3 Dec 2020 08:50:35 +0800 [thread overview]
Message-ID: <20201203005035.GA540033@T590> (raw)
In-Reply-To: <b70f46b855858a28b0e77ee7efbb2dbffbb56490.camel@redhat.com>
On Wed, Dec 02, 2020 at 02:07:08PM -0500, Qian Cai wrote:
> On Mon, 2020-11-30 at 10:36 +0800, Ming Lei wrote:
> > Any chance to take a look? And this issue has been reported several
> > times in RH internal test.
>
> I suppose that you will need to rebase as it does not apply cleanly on today's
> linux-next.
>
I just apply the three patches against for-5.11/block, and they can be
done cleanly.
Thanks,
Ming
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2020-12-03 0:52 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 7:55 [PATCH 0/3] blk-mq/nvme-loop: use nvme-loop's lock class for addressing lockdep false positive warning Ming Lei
2020-11-12 7:55 ` Ming Lei
2020-11-12 7:55 ` [PATCH 1/3] blk-mq: add new API of blk_mq_hctx_set_fq_lock_class Ming Lei
2020-11-12 7:55 ` Ming Lei
2020-11-16 17:26 ` Christoph Hellwig
2020-11-16 17:26 ` Christoph Hellwig
2020-11-17 1:04 ` Ming Lei
2020-11-17 1:04 ` Ming Lei
2020-11-17 1:16 ` Ming Lei
2020-11-17 1:16 ` Ming Lei
2020-11-17 6:46 ` Kashyap Desai
2020-11-17 6:46 ` Kashyap Desai
2020-11-12 7:55 ` [PATCH 2/3] nvme-loop: use blk_mq_hctx_set_fq_lock_class to set loop's lock class Ming Lei
2020-11-12 7:55 ` Ming Lei
2020-11-16 17:27 ` Christoph Hellwig
2020-11-16 17:27 ` Christoph Hellwig
2020-11-12 7:55 ` [PATCH 3/3] Revert "block: Fix a lockdep complaint triggered by request queue flushing" Ming Lei
2020-11-12 7:55 ` Ming Lei
2020-11-12 15:12 ` Bart Van Assche
2020-11-12 15:12 ` Bart Van Assche
2020-11-12 15:29 ` Bart Van Assche
2020-11-12 15:29 ` Bart Van Assche
2020-11-13 1:11 ` Ming Lei
2020-11-13 1:11 ` Ming Lei
2020-11-13 1:27 ` [PATCH V2 " Ming Lei
2020-11-13 1:27 ` Ming Lei
2020-11-16 17:27 ` Christoph Hellwig
2020-11-16 17:27 ` Christoph Hellwig
2020-11-25 1:31 ` [PATCH 0/3] blk-mq/nvme-loop: use nvme-loop's lock class for addressing lockdep false positive warning Ming Lei
2020-11-25 1:31 ` Ming Lei
2020-11-30 2:36 ` Ming Lei
2020-11-30 2:36 ` Ming Lei
2020-12-02 19:07 ` Qian Cai
2020-12-02 19:07 ` Qian Cai
2020-12-03 0:50 ` Ming Lei [this message]
2020-12-03 0:50 ` Ming Lei
2020-12-03 1:23 ` Qian Cai
2020-12-03 1:23 ` Qian Cai
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=20201203005035.GA540033@T590 \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=john.garry@huawei.com \
--cc=kashyap.desai@broadcom.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=qcai@redhat.com \
--cc=sumit.saxena@broadcom.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.