From: hch@infradead.org (Christoph Hellwig)
Subject: nvme-cli won't build
Date: Tue, 27 Sep 2016 07:50:13 -0700 [thread overview]
Message-ID: <20160927145013.GA5310@infradead.org> (raw)
In-Reply-To: <20160926221544.GA6978@infradead.org>
The patch below will fix it for you:
diff --git a/linux/nvme.h b/linux/nvme.h
index c3ed1df..30a4c00 100644
--- a/linux/nvme.h
+++ b/linux/nvme.h
@@ -16,7 +16,6 @@
#define _LINUX_NVME_H
#include <linux/types.h>
-#include <linux/uuid.h>
/* NQN names in commands fields specified one size */
#define NVMF_NQN_FIELD_LEN 256
@@ -803,7 +802,7 @@ struct nvmf_connect_command {
};
struct nvmf_connect_data {
- uuid_be hostid;
+ __u8 hostid[16];
__le16 cntlid;
char resv4[238];
char subsysnqn[NVMF_NQN_FIELD_LEN];
next prev parent reply other threads:[~2016-09-27 14:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-26 22:13 nvme-cli won't build Steve Wise
2016-09-26 22:15 ` Christoph Hellwig
2016-09-27 14:50 ` Christoph Hellwig [this message]
2016-09-27 14:54 ` Steve Wise
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=20160927145013.GA5310@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 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.