From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH v2] nvme: call nvme_complete_rq on NVME_MPATH failures
Date: Fri, 28 Sep 2018 18:00:47 -0700 [thread overview]
Message-ID: <20180929010047.GA23662@infradead.org> (raw)
In-Reply-To: <20180927235854.12386-1-jsmart2021@gmail.com>
Thanks,
applied for nvme-4.20.
next prev parent reply other threads:[~2018-09-29 1:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 23:58 [PATCH v2] nvme: call nvme_complete_rq on NVME_MPATH failures James Smart
2018-09-28 22:43 ` Sagi Grimberg
2018-09-29 1:00 ` Christoph Hellwig [this message]
2018-09-29 12:13 ` Hannes Reinecke
2018-09-30 16:33 ` James Smart
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=20180929010047.GA23662@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).