From: james_p_freyensee@linux.intel.com (J Freyensee)
Subject: [PATCH v3 2/7] nvme-fabrics: Add FC transport error codes to nvme.h
Date: Tue, 25 Oct 2016 16:48:13 -0700 [thread overview]
Message-ID: <1477439293.3009.79.camel@linux.intel.com> (raw)
In-Reply-To: <20161025163628.GB2446@infradead.org>
On Tue, 2016-10-25@09:36 -0700, Christoph Hellwig wrote:
> Looks fine,
>
> Reviewed-by: Christoph Hellwig <hch at lst.de>
>
Also looks fine,
Reviewed-by: Jay Freyensee <james_p_freyensee at linux.intel.com>
> _______________________________________________
> Linux-nvme mailing list
> Linux-nvme at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-nvme
prev parent reply other threads:[~2016-10-25 23:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-23 19:31 [PATCH v3 2/7] nvme-fabrics: Add FC transport error codes to nvme.h James Smart
2016-10-25 16:36 ` Christoph Hellwig
2016-10-25 23:48 ` J Freyensee [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=1477439293.3009.79.camel@linux.intel.com \
--to=james_p_freyensee@linux.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;
as well as URLs for NNTP newsgroup(s).