From: bvanassche@acm.org (Bart Van Assche)
Subject: [PATCH RFC] nvmet-rdma: use a private workqueue for delete
Date: Mon, 22 Oct 2018 14:17:26 -0700 [thread overview]
Message-ID: <1540243046.128590.28.camel@acm.org> (raw)
In-Reply-To: <972d73ea2043fe755e9a5d9be649bb15a88378e7.camel@sipsolutions.net>
On Mon, 2018-10-22@10:56 +0200, Johannes Berg wrote:
> On Fri, 2018-10-19@16:23 +0000, Bart Van Assche wrote:
> > On Thu, 2018-10-18@18:08 -0700, Sagi Grimberg wrote:
> > > > It seems like this has not yet been fixed entirely. This is what appeared
> > > > in the kernel log this morning on my test setup with Christoph's nvme-4.20
> > > > branch (commit cb4bfda62afa ("nvme-pci: fix hot removal during error
> > > > handling")):
>
> FWIW, I'm not sure where to find this tree (it's not on kernel.org,
> apparently, at least none of hch's?). As a result, I don't have the
> correct code here now.
Christoph's NVMe tree is available at git://git.infradead.org/nvme.git.
Bart.
next prev parent reply other threads:[~2018-10-22 21:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 18:00 [PATCH RFC] nvmet-rdma: use a private workqueue for delete Sagi Grimberg
2018-09-28 22:14 ` Bart Van Assche
2018-10-01 20:12 ` Sagi Grimberg
2018-10-02 15:02 ` Bart Van Assche
2018-10-05 7:25 ` Christoph Hellwig
[not found] ` <CAO+b5-oBVw=-wvnWk1EF=RBaZtjX6bjUG+3WABXbvzX9UTu26w@mail.gmail.com>
2018-10-19 1:08 ` Sagi Grimberg
2018-10-19 16:23 ` Bart Van Assche
2018-10-22 8:56 ` Johannes Berg
2018-10-22 21:17 ` Bart Van Assche [this message]
2018-10-23 19:18 ` Johannes Berg
2018-10-23 19:54 ` Bart Van Assche
2018-10-23 19:59 ` Johannes Berg
2018-10-23 20:00 ` Johannes Berg
2018-10-23 0:40 ` Sagi Grimberg
2018-10-23 19:22 ` Johannes Berg
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=1540243046.128590.28.camel@acm.org \
--to=bvanassche@acm.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).