From: "Michael S. Tsirkin" <mst@redhat.com>
To: Paul Durrant <paul.durrant@citrix.com>
Cc: xen-devel@lists.xenproject.org, qemu-devel@nongnu.org,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [Qemu-devel] [PATCH] Fix the compatibility typedef of ioservid_t to match the Xen headers
Date: Wed, 8 Jul 2015 17:06:09 +0300 [thread overview]
Message-ID: <20150708170556-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <1436275958-25174-1-git-send-email-paul.durrant@citrix.com>
On Tue, Jul 07, 2015 at 02:32:38PM +0100, Paul Durrant wrote:
> There is a mismatch between the definition of ioservid_t in
> xen_common.h and the definition in the Xen publix headers. This patch
> corrects the definition in xen_common.h.
>
> Signed-off-by: Paul Durrant <paul.durrant@citrix.com>
> Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Tested-by: Michael S. Tsirkin <mst@redhat.com>
> ---
> include/hw/xen/xen_common.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/hw/xen/xen_common.h b/include/hw/xen/xen_common.h
> index 38f29fb..ed5fd3e 100644
> --- a/include/hw/xen/xen_common.h
> +++ b/include/hw/xen/xen_common.h
> @@ -195,7 +195,7 @@ static inline int xen_get_vmport_regs_pfn(XenXC xc, domid_t dom,
>
> #define IOREQ_TYPE_PCI_CONFIG 2
>
> -typedef uint32_t ioservid_t;
> +typedef uint16_t ioservid_t;
>
> static inline void xen_map_memory_section(XenXC xc, domid_t dom,
> ioservid_t ioservid,
> --
> 1.7.10.4
next prev parent reply other threads:[~2015-07-08 14:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 13:32 [Qemu-devel] [PATCH] Fix the compatibility typedef of ioservid_t to match the Xen headers Paul Durrant
2015-07-08 14:06 ` Michael S. Tsirkin [this message]
2015-07-08 15:47 ` Peter Maydell
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=20150708170556-mutt-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=paul.durrant@citrix.com \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).