From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] nvme: introduce nvme_is_fabrics to check fabrics cmd
Date: Thu, 6 Jun 2019 08:34:17 +0200 [thread overview]
Message-ID: <20190606063417.GA27033@lst.de> (raw)
In-Reply-To: <20190606053014.27240-1-minwoo.im.dev@gmail.com>
On Thu, Jun 06, 2019@02:30:14PM +0900, Minwoo Im wrote:
> This patch introduces a nvme_is_fabrics() inline function to check
> whether or not the given command structure is for fabrics.
Looks good,
Reviewed-by: Christoph Hellwig <hch at lst.de>
next prev parent reply other threads:[~2019-06-06 6:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 5:30 [PATCH] nvme: introduce nvme_is_fabrics to check fabrics cmd Minwoo Im
2019-06-06 6:34 ` Christoph Hellwig [this message]
2019-06-06 6:58 ` Sagi Grimberg
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=20190606063417.GA27033@lst.de \
--to=hch@lst.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.