From: Ian Campbell <ian.campbell@citrix.com>
To: xen-devel@lists.xensource.com
Cc: ian.jackson@citrix.com
Subject: [PATCH 00 of 20] libxl: drop device_model_info
Date: Mon, 23 Jan 2012 16:45:23 +0000 [thread overview]
Message-ID: <patchbomb.1327337123@cosworth.uk.xensource.com> (raw)
This is the first portion of my previous "libxl: drop
device_model_info, better defaults support, stubdoms by default"
series. Specifically it is the "drop device_model_info" bit (plus some
incidental bits & bobs).
I've split it to make it all a bit more manageable and to allow it to
be reviewed while I address some other concerns with the latter bits
of the other series.
This comes after "libxl: tweak the cpupool interface slightly" which I
sent this morning in my queue but I think the only relation is a tiny
bit of overlap of the context in patch #2. It also comes after "libxl:
remove _libxl_json_internal.h from libxl_json.h" but I beleive there
is no overlap there.
Ian.
next reply other threads:[~2012-01-23 16:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-23 16:45 Ian Campbell [this message]
2012-01-23 16:45 ` [PATCH 01 of 20] libxl: remove comment support from IDL Ian Campbell
2012-01-23 16:45 ` [PATCH 02 of 20] libxl: use keyword arguments for field definitions in aggregate types Ian Campbell
2012-01-23 16:45 ` [PATCH 03 of 20] ocaml: use libxl IDL type helpers for C argument passing Ian Campbell
2012-01-31 14:36 ` Ian Jackson
2012-01-23 16:45 ` [PATCH 04 of 20] libxl: define libxl_vnc_info to hold all info about the vnc info Ian Campbell
2012-01-23 16:45 ` [PATCH 05 of 20] libxl: define libxl_spice_info to hold all info about the spice server Ian Campbell
2012-01-23 16:45 ` [PATCH 06 of 20] libxl: define libxl_sdl_info to hold all info about the SDL config Ian Campbell
2012-01-23 16:45 ` [PATCH 07 of 20] libxl: plumb libxl_domain_config down into device model creation Ian Campbell
2012-01-23 16:45 ` [PATCH 08 of 20] libxl: now that dm creation takes domain_config stop passing down devices Ian Campbell
2012-01-31 14:45 ` Ian Jackson
2012-01-23 16:45 ` [PATCH 09 of 20] libxl: remove redundant info from dm info Ian Campbell
2012-01-23 16:45 ` [PATCH 10 of 20] libxl: drop dm_info.dom_name Ian Campbell
2012-01-23 16:45 ` [PATCH 11 of 20] libxl: use vfb[0] directly for xenpv device model Ian Campbell
2012-01-23 16:45 ` [PATCH 12 of 20] libxl: move HVM emulated GFX support into b_info->u.hvm Ian Campbell
2012-01-23 16:45 ` [PATCH 13 of 20] libxl: HVM device configuration info build_info->u.hvm Ian Campbell
2012-01-23 16:45 ` [PATCH 14 of 20] libxl: move gfx_passthru setting to b_info->u.hvm Ian Campbell
2012-01-23 16:45 ` [PATCH 15 of 20] libxl: Remove libxl_device_model_info.type Ian Campbell
2012-01-23 16:45 ` [PATCH 16 of 20] libxl: remove uuid from device model info Ian Campbell
2012-01-23 16:45 ` [PATCH 17 of 20] libxl: move device model selection variables to b_info Ian Campbell
2012-01-31 15:28 ` Ian Jackson
2012-01-31 15:38 ` Ian Campbell
2012-01-23 16:45 ` [PATCH 18 of 20] libxl: move "saved_state" to libxl__domain_build_state Ian Campbell
2012-01-23 16:45 ` [PATCH 19 of 20] libxl: remove libxl_device_model_info Ian Campbell
2012-01-23 16:45 ` [PATCH 20 of 20] libxl: only write "disable_pf" key to xenstore when it makes sense Ian Campbell
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=patchbomb.1327337123@cosworth.uk.xensource.com \
--to=ian.campbell@citrix.com \
--cc=ian.jackson@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 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).