From: Will Deacon <will.deacon@arm.com>
To: penberg@kernel.org
Cc: kvm@vger.kernel.org, Marc Zyngier <marc.zyngier@arm.com>,
Will Deacon <will.deacon@arm.com>
Subject: [PATCH 2/2] kvm tools: 9p: fix compilation broken by new stat structures
Date: Mon, 4 Mar 2013 06:27:31 +0000 [thread overview]
Message-ID: <1362378451-15216-2-git-send-email-will.deacon@arm.com> (raw)
In-Reply-To: <1362378451-15216-1-git-send-email-will.deacon@arm.com>
From: Marc Zyngier <marc.zyngier@arm.com>
Commit 447c50943fd0 ("9p: Modify the stat structures to use kuid_t and
kgid_t") broke the 9p backend by introducing the k{u,g}id_t types, which
aren't currently in scope.
Just fix the damn thing by including linux/uidgid.h.
Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Signed-off-by: Will Deacon <will.deacon@arm.com>
---
tools/kvm/virtio/9p-pdu.c | 1 +
tools/kvm/virtio/9p.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/tools/kvm/virtio/9p-pdu.c b/tools/kvm/virtio/9p-pdu.c
index b9ce8ce..9e95f3b 100644
--- a/tools/kvm/virtio/9p-pdu.c
+++ b/tools/kvm/virtio/9p-pdu.c
@@ -5,6 +5,7 @@
#include <stdint.h>
#include <linux/compiler.h>
+#include <linux/uidgid.h>
#include <net/9p/9p.h>
static void virtio_p9_pdu_read(struct p9_pdu *pdu, void *data, size_t size)
diff --git a/tools/kvm/virtio/9p.c b/tools/kvm/virtio/9p.c
index 60865dd..b7a5723 100644
--- a/tools/kvm/virtio/9p.c
+++ b/tools/kvm/virtio/9p.c
@@ -18,6 +18,7 @@
#include <linux/virtio_ring.h>
#include <linux/virtio_9p.h>
+#include <linux/uidgid.h>
#include <net/9p/9p.h>
static LIST_HEAD(devs);
--
1.8.0
next prev parent reply other threads:[~2013-03-04 6:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 6:27 [PATCH 1/2] kvm tools: init: fix usage of hlist iterators Will Deacon
2013-03-04 6:27 ` Will Deacon [this message]
2013-03-04 15:33 ` Will Deacon
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=1362378451-15216-2-git-send-email-will.deacon@arm.com \
--to=will.deacon@arm.com \
--cc=kvm@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=penberg@kernel.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