From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH] NVMe-CLI Fixed Status Code check for reset type on fw-activate.
Date: Tue, 12 Sep 2017 13:48:24 -0400 [thread overview]
Message-ID: <20170912174824.GC2832@localhost.localdomain> (raw)
In-Reply-To: <1505237825-21002-1-git-send-email-jeff.lien@wdc.com>
Thanks, applied.
Don't forget your 'Signed-off-by' for next time. :)
prev parent reply other threads:[~2017-09-12 17:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 17:37 [PATCH] NVMe-CLI Fixed Status Code check for reset type on fw-activate jeffreyalien
2017-09-12 17:48 ` 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=20170912174824.GC2832@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