From: james_p_freyensee@linux.intel.com (J Freyensee)
Subject: [PATCH 2/5] nvme.h: don't use uuid_be
Date: Mon, 03 Oct 2016 09:10:15 -0700 [thread overview]
Message-ID: <1475511015.2510.10.camel@linux.intel.com> (raw)
In-Reply-To: <1475236270-18329-3-git-send-email-hch@lst.de>
On Fri, 2016-09-30@13:51 +0200, Christoph Hellwig wrote:
> This makes life easier for nvme-cli and we don't really need the uuid
> type anyway to start with.
>
> Signed-off-by: Christoph Hellwig <hch at lst.de>
Looks good,
Reviewed-by: Jay Freyensee <james_p_freyensee at linux.intel.com>
next prev parent reply other threads:[~2016-10-03 16:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-30 11:51 nvme header updates Christoph Hellwig
2016-09-30 11:51 ` [PATCH 1/5] nvme.h: resync with nvme-cli Christoph Hellwig
2016-09-30 11:51 ` [PATCH 2/5] nvme.h: don't use uuid_be Christoph Hellwig
2016-10-03 16:10 ` J Freyensee [this message]
2016-09-30 11:51 ` [PATCH 3/5] nvme.h: add an enum for cns values Christoph Hellwig
2016-09-30 15:19 ` Keith Busch
2016-09-30 11:51 ` [PATCH 4/5] nvme: use symbolic constants for CNS values Christoph Hellwig
2016-09-30 15:20 ` Keith Busch
2016-09-30 11:51 ` [PATCH 5/5] nvmet: " Christoph Hellwig
2016-10-03 16:09 ` J Freyensee
2016-09-30 13:07 ` nvme header updates Gabriel Krisman Bertazi
2016-10-19 16:53 ` Christoph Hellwig
2016-10-19 17:01 ` Jens Axboe
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=1475511015.2510.10.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 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.