From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH 2/2] NVMe: Simplify device resume on io queue failure
Date: Fri, 2 Oct 2015 06:03:34 -0700 [thread overview]
Message-ID: <20151002130334.GB11175@infradead.org> (raw)
In-Reply-To: <1443741251-13274-3-git-send-email-keith.busch@intel.com>
On Thu, Oct 01, 2015@05:14:11PM -0600, Keith Busch wrote:
> this patch removes the unnecessary indirection, and places all work
> tasks onto the global work queue.
Can you explain why nvme_workq is removed here? I don't really
understand why it's realted, but that might be because I don't
even know why it exists in the first place. Maybe this should be a
separate patch with a separate changelog entry?
Otherwise looks good,
Reviewed-by: Christoph Hellwig <hch at lst.de>
next prev parent reply other threads:[~2015-10-02 13:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 23:14 [PATCH 0/2] Namespace attachment fixes/simplifications Keith Busch
2015-10-01 23:14 ` [PATCH 1/2] NVMe: Reference count open namespaces Keith Busch
2015-10-02 12:59 ` Christoph Hellwig
2015-10-02 14:26 ` Keith Busch
2015-10-02 14:31 ` Christoph Hellwig
2015-10-01 23:14 ` [PATCH 2/2] NVMe: Simplify device resume on io queue failure Keith Busch
2015-10-02 13:03 ` Christoph Hellwig [this message]
2015-10-02 14:17 ` Keith Busch
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=20151002130334.GB11175@infradead.org \
--to=hch@infradead.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).