From: sagi@grimberg.me (Sagi Grimberg)
Subject: [RFC PATCH] nvme of: don't flush scan work inside reset context
Date: Wed, 7 Nov 2018 10:38:44 -0800 [thread overview]
Message-ID: <5f193243-a0a7-8f9f-7d7b-7f3f87a7fdae@grimberg.me> (raw)
In-Reply-To: <20181107083412.GA8878@ming.t460p>
> https://bugzilla.redhat.com/show_bug.cgi?id=1622487
> https://bugzilla.redhat.com/show_bug.cgi?id=1628100
>
> Especially you may find some details in the following comment:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1628100#c7
I don't have permissions to see the tickets.
next prev parent reply other threads:[~2018-11-07 18:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 11:57 [RFC PATCH] nvme of: don't flush scan work inside reset context Ming Lei
2018-11-05 16:28 ` Keith Busch
2018-11-06 0:30 ` Ming Lei
2018-11-05 20:04 ` James Smart
2018-11-06 1:18 ` Ming Lei
2018-11-06 5:45 ` James Smart
2018-11-07 1:58 ` Ming Lei
2018-11-08 0:19 ` Sagi Grimberg
2018-11-08 17:49 ` James Smart
2018-11-07 3:26 ` Sagi Grimberg
2018-11-07 3:51 ` Ming Lei
2018-11-07 4:38 ` Sagi Grimberg
2018-11-07 8:34 ` Ming Lei
2018-11-07 18:38 ` Sagi Grimberg [this message]
2018-11-07 19:27 ` James Smart
2018-11-08 0:05 ` Ming Lei
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=5f193243-a0a7-8f9f-7d7b-7f3f87a7fdae@grimberg.me \
--to=sagi@grimberg.me \
/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).