From: Stefan Berger <stefanb@us.ibm.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: [PATCH] [ACM] Comilation fix for 32 bit
Date: Wed, 25 Apr 2007 23:36:38 -0400 [thread overview]
Message-ID: <1177558598.4833.1.camel@941e-2.watson.ibm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 84 bytes --]
This fixes a compilation problem on 32 bit machines.
Signed-off-by: Stefan Berger
[-- Attachment #2: acm_buffer_type.diff --]
[-- Type: text/x-patch, Size: 1126 bytes --]
Index: root/xen-unstable.hg/xen/include/public/acm_ops.h
===================================================================
--- root.orig/xen-unstable.hg/xen/include/public/acm_ops.h
+++ root/xen-unstable.hg/xen/include/public/acm_ops.h
@@ -50,7 +50,7 @@
struct acm_setpolicy {
/* IN */
uint32_t interface_version;
- XEN_GUEST_HANDLE_64(void) pushcache;
+ XEN_GUEST_HANDLE(void) pushcache;
uint32_t pushcache_size;
};
@@ -59,7 +59,7 @@ struct acm_setpolicy {
struct acm_getpolicy {
/* IN */
uint32_t interface_version;
- XEN_GUEST_HANDLE_64(void) pullcache;
+ XEN_GUEST_HANDLE(void) pullcache;
uint32_t pullcache_size;
};
@@ -68,7 +68,7 @@ struct acm_getpolicy {
struct acm_dumpstats {
/* IN */
uint32_t interface_version;
- XEN_GUEST_HANDLE_64(void) pullcache;
+ XEN_GUEST_HANDLE(void) pullcache;
uint32_t pullcache_size;
};
@@ -84,7 +84,7 @@ struct acm_getssid {
domaintype_t domainid;
ssidref_t ssidref;
} id;
- XEN_GUEST_HANDLE_64(void) ssidbuf;
+ XEN_GUEST_HANDLE(void) ssidbuf;
uint32_t ssidbuf_size;
};
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2007-04-26 3:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 3:36 Stefan Berger [this message]
2007-04-26 6:50 ` [PATCH] [ACM] Comilation fix for 32 bit Keir Fraser
2007-04-26 10:49 ` Stefan Berger
2007-04-26 10:55 ` Keir Fraser
2007-04-26 10:59 ` Stefan Berger
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=1177558598.4833.1.camel@941e-2.watson.ibm.com \
--to=stefanb@us.ibm.com \
--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 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.