From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH] nvme: fc: provide a descriptive error
Date: Mon, 23 Apr 2018 12:24:51 -0600 [thread overview]
Message-ID: <20180423182450.GD19048@localhost.localdomain> (raw)
In-Reply-To: <500112aa-ea97-2428-ac39-854329a52e93@suse.de>
Thanks, staged for 4.18.
prev parent reply other threads:[~2018-04-23 18:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 17:43 [PATCH] nvme: fc: provide a descriptive error Johannes Thumshirn
2018-04-19 21:20 ` James Smart
2018-04-20 5:43 ` Hannes Reinecke
2018-04-23 18:24 ` Keith Busch [this message]
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=20180423182450.GD19048@localhost.localdomain \
--to=keith.busch@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox