From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH] nvme-fabrics: change NQN UUID to big-endian format
Date: Wed, 29 Jun 2016 23:41:53 -0700 [thread overview]
Message-ID: <20160630064153.GA27456@infradead.org> (raw)
In-Reply-To: <1467138023-41671-1-git-send-email-daniel.verkamp@intel.com>
On Tue, Jun 28, 2016@11:20:23AM -0700, Daniel Verkamp wrote:
> NVM Express 1.2.1 section 7.9, NVMe Qualified Names, specifies that the
> UUID format of NQN uses a UUID based on RFC 4122.
>
> RFC 4122 specifies that the UUID is encoded in big-endian byte order.
>
> Switch the NVMe over Fabrics host ID field from little-endian UUID to
> big-endian UUID to match the specification.
>
> Signed-off-by: Daniel Verkamp <daniel.verkamp at intel.com>
Thanks a lot Daniel, I'll send this on to Jens.
next prev parent reply other threads:[~2016-06-30 6:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 18:22 NVMe over Fabrics: NQN UUID byte order Verkamp, Daniel
2016-06-28 8:45 ` Christoph Hellwig
2016-06-28 18:20 ` [PATCH] nvme-fabrics: change NQN UUID to big-endian format Daniel Verkamp
2016-06-28 19:55 ` Freyensee, James P
2016-06-30 6:41 ` Christoph Hellwig [this message]
2016-08-18 19:48 ` Verkamp, Daniel
2016-08-19 9:02 ` Sagi Grimberg
2016-07-13 10:12 ` 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=20160630064153.GA27456@infradead.org \
--to=hch@infradead.org \
/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).