From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH, nvme-cli] fix build without libuuid
Date: Wed, 28 Jun 2017 16:09:12 -0700 [thread overview]
Message-ID: <20170628230912.1598-1-hch@lst.de> (raw)
Signed-off-by: Christoph Hellwig <hch at lst.de>
---
nvme.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/nvme.h b/nvme.h
index b796961..5530f90 100644
--- a/nvme.h
+++ b/nvme.h
@@ -17,6 +17,7 @@
#include <stdbool.h>
#include <endian.h>
+#include <stdint.h>
#include "plugin.h"
#include "json.h"
@@ -26,7 +27,7 @@
#include <uuid/uuid.h>
#else
typedef struct {
- __u8 b[16];
+ uint8_t b[16];
} uuid_t;
#endif
--
2.11.0
next reply other threads:[~2017-06-28 23:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 23:09 Christoph Hellwig [this message]
2017-06-29 17:44 ` [PATCH, nvme-cli] fix build without libuuid Keith Busch
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=20170628230912.1598-1-hch@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox