From: Gerd Hoffmann <kraxel@redhat.com>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: Xen Development Mailing List <xen-devel@lists.xensource.com>
Subject: [Qemu-devel] include inttypes.h in xen.h
Date: Thu, 28 May 2009 13:29:08 +0200 [thread overview]
Message-ID: <4A1E7584.7070005@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 78 bytes --]
Hi,
xen.h uses uint32_t, so make sure it is known.
please apply,
Gerd
[-- Attachment #2: 0003-include-inttypes.h-in-xen.h.patch --]
[-- Type: text/plain, Size: 637 bytes --]
>From d8d81a9d4aa0a760ad04df7db95387a3229dbcb1 Mon Sep 17 00:00:00 2001
From: Gerd Hoffmann <kraxel@redhat.com>
Date: Wed, 13 May 2009 11:20:50 +0200
Subject: [PATCH 03/21] include inttypes.h in xen.h
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
---
hw/xen.h | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/hw/xen.h b/hw/xen.h
index 3c8da41..780dcf7 100644
--- a/hw/xen.h
+++ b/hw/xen.h
@@ -6,6 +6,7 @@
* must not depend on any xen headers being present in
* /usr/include/xen, so it can be included unconditionally.
*/
+#include <inttypes.h>
/* xen-machine.c */
enum xen_mode {
--
1.6.2.2
reply other threads:[~2009-05-28 11:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4A1E7584.7070005@redhat.com \
--to=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=xen-devel@lists.xensource.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 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).