The C spec identifies stdint.h as freestanding, and available for use in
non-hosted environments, such as Xen.

Signed-off-by: Andrew Cooper <andrew.coop...@citrix.com>
---
CC: George Dunlap <george.dun...@eu.citrix.com>
CC: Ian Jackson <ian.jack...@eu.citrix.com>
CC: Jan Beulich <jbeul...@suse.com>
CC: Konrad Rzeszutek Wilk <konrad.w...@oracle.com>
CC: Stefano Stabellini <sstabell...@kernel.org>
CC: Tim Deegan <t...@xen.org>
CC: Wei Liu <wei.l...@citrix.com>
---
 xen/crypto/vmac.c       |  1 -
 xen/include/xen/types.h | 12 +-----------
 2 files changed, 1 insertion(+), 12 deletions(-)

diff --git a/xen/crypto/vmac.c b/xen/crypto/vmac.c
index f3f2743..db555b3 100644
--- a/xen/crypto/vmac.c
+++ b/xen/crypto/vmac.c
@@ -12,7 +12,6 @@
 #include <xen/types.h>
 #include <xen/lib.h>
 #include <crypto/vmac.h>
-#define UINT64_C(x)  x##ULL
 /* end for Xen */
 
 /* Enable code tuned for 64-bit registers; otherwise tuned for 32-bit */
diff --git a/xen/include/xen/types.h b/xen/include/xen/types.h
index 384a02f..1ff534d 100644
--- a/xen/include/xen/types.h
+++ b/xen/include/xen/types.h
@@ -3,6 +3,7 @@
 
 /* Use the C freestanding headers. */
 #include <stdarg.h>
+#include <stdint.h>
 
 #include <asm/types.h>
 
@@ -34,21 +35,10 @@ typedef unsigned short          ushort;
 typedef unsigned int            uint;
 typedef unsigned long           ulong;
 
-typedef         __u8            uint8_t;
 typedef         __u8            u_int8_t;
-typedef         __s8            int8_t;
-
-typedef         __u16           uint16_t;
 typedef         __u16           u_int16_t;
-typedef         __s16           int16_t;
-
-typedef         __u32           uint32_t;
 typedef         __u32           u_int32_t;
-typedef         __s32           int32_t;
-
-typedef         __u64           uint64_t;
 typedef         __u64           u_int64_t;
-typedef         __s64           int64_t;
 
 struct domain;
 struct vcpu;
-- 
2.1.4


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Reply via email to