From: Ian Jackson <Ian.Jackson@eu.citrix.com>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH 0 of 6 V2] libxl: IDL improvements
Date: Mon, 18 Jul 2011 17:11:54 +0100 [thread overview]
Message-ID: <20004.23370.445860.65030@mariner.uk.xensource.com> (raw)
In-Reply-To: <patchbomb.1310997429@localhost.localdomain>
Ian Campbell writes ("[Xen-devel] [PATCH 0 of 6 V2] libxl: IDL improvements"):
> Shave various yacks for Ian J ;-)
>
> * LIBXL_DOMAIN_TYPE_FV -> LIBXL_DOMAIN_TYPE_HVM
> * Make more use of libxl_domain_type enum:
> * replace libxl__domain_is_hvm with libxl__domain_type
> * use in IDL in preference to 'bool hvm'
> * KeyedUnion keyvar must now be a Enumeration.
>
> V2:
> post a version which applies without needing my WIP JSON series.
Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
Committed-by: Ian Jackson <ian.jackson@eu.citrix.com>
Thanks!
Ian.
prev parent reply other threads:[~2011-07-18 16:11 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-12 18:37 [RFC 0/3] libxl event handling Ian Jackson
2011-07-12 18:37 ` [PATCH 1/3] RFC: libxl: API changes re domain type (and keyed union semantics) Ian Jackson
2011-07-12 18:37 ` [PATCH 2/3] RFC: libxl: API changes re event handling Ian Jackson
2011-07-12 18:37 ` [PATCH 3/3] RFC: libxl: internal API for " Ian Jackson
2011-07-13 10:22 ` Ian Campbell
2011-07-13 10:21 ` [PATCH 2/3] RFC: libxl: API changes re " Ian Campbell
2011-07-13 14:03 ` Ian Jackson
2011-07-13 16:08 ` Ian Campbell
2011-07-13 16:17 ` Ian Jackson
2011-07-13 16:33 ` Ian Campbell
2011-07-13 17:04 ` Ian Jackson
2011-07-13 9:19 ` [PATCH 1/3] RFC: libxl: API changes re domain type (and keyed union semantics) Ian Campbell
2011-07-15 12:45 ` Ian Campbell
2011-07-15 13:13 ` Ian Jackson
2011-07-18 9:06 ` [PATCH 0 of 6] libxl: IDL improvements Ian Campbell
2011-07-18 9:06 ` [PATCH 1 of 6] libxl: Give the HVM domain type the name "HVM" Ian Campbell
2011-07-18 9:06 ` [PATCH 2 of 6] libxl: replace libxl__domain_is_hvm with libxl__domain_type Ian Campbell
2011-07-18 9:06 ` [PATCH 3 of 6] libxl: specify HVM vs PV in build_info using libxl_domain_type enum Ian Campbell
2011-07-18 9:06 ` [PATCH 4 of 6] libxl: specify HVM vs PV in create_info " Ian Campbell
2011-07-18 9:06 ` [PATCH 5 of 6] libxl: use libxl_domain_type enum with libxl__domain_suspend_common Ian Campbell
2011-07-18 9:06 ` [PATCH 6 of 6] libxl: Keyed unions key off an enum instead of an arbitrary expression Ian Campbell
2011-07-18 13:57 ` [PATCH 0 of 6 V2] libxl: IDL improvements Ian Campbell
2011-07-18 13:57 ` [PATCH 1 of 6 V2] libxl: Give the HVM domain type the name "HVM" Ian Campbell
2011-07-18 14:56 ` Wei LIU
2011-07-18 15:20 ` Ian Jackson
2011-07-18 13:57 ` [PATCH 2 of 6 V2] libxl: replace libxl__domain_is_hvm with libxl__domain_type Ian Campbell
2011-07-18 13:57 ` [PATCH 3 of 6 V2] libxl: specify HVM vs PV in build_info using libxl_domain_type enum Ian Campbell
2011-07-18 13:57 ` [PATCH 4 of 6 V2] libxl: specify HVM vs PV in create_info " Ian Campbell
2011-07-18 13:57 ` [PATCH 5 of 6 V2] libxl: use libxl_domain_type enum with libxl__domain_suspend_common Ian Campbell
2011-07-18 13:57 ` [PATCH 6 of 6 V2] libxl: Keyed unions key off an enum instead of an arbitrary expression Ian Campbell
2011-07-18 16:11 ` Ian Jackson [this message]
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=20004.23370.445860.65030@mariner.uk.xensource.com \
--to=ian.jackson@eu.citrix.com \
--cc=ian.campbell@citrix.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.