From: Vincent Hanquez <vincent.hanquez@eu.citrix.com>
To: xen-devel@lists.xensource.com
Cc: Vincent Hanquez <vincent.hanquez@eu.citrix.com>
Subject: [PATCH 0/5] more solidification work
Date: Wed, 13 Jan 2010 16:14:50 +0000 [thread overview]
Message-ID: <1263399295-19453-1-git-send-email-vincent.hanquez@eu.citrix.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 883 bytes --]
more solidification work around return values in stubdom,
invalid device kinds, and fix name to domid. nothing
ground breaking but quite nice to have.
Vincent Hanquez (5):
add some return values testing in stubdom
initialize enum to 1, to prevent defaulting to the 0 values when
structure when not properly initialized by the client.
add fuse around generic_device_add related to invalid kinds
add error in disk_add if phystype is not recognized
fix name to domid conversion.
tools/libxl/libxl.c | 38 ++++++++++++++++++++++++++++----------
tools/libxl/libxl.h | 6 +++---
tools/libxl/libxl_device.c | 5 ++++-
tools/libxl/libxl_internal.h | 4 ++--
tools/libxl/libxl_utils.c | 33 +++++++++++----------------------
tools/libxl/xl.c | 4 +---
6 files changed, 49 insertions(+), 41 deletions(-)
[-- Attachment #2: 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:[~2010-01-13 16:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 16:14 Vincent Hanquez [this message]
2010-01-13 16:14 ` [PATCH 1/5] add some return values testing in stubdom Vincent Hanquez
2010-01-13 16:14 ` [PATCH 2/5] initialize enum to 1, to prevent defaulting to the 0 values when structure when not properly initialized by the client Vincent Hanquez
2010-01-13 16:14 ` [PATCH 3/5] add fuse around generic_device_add related to invalid kinds Vincent Hanquez
2010-01-13 16:14 ` [PATCH 4/5] add error in disk_add if phystype is not recognized Vincent Hanquez
2010-01-13 16:14 ` [PATCH 5/5] fix name to domid conversion Vincent Hanquez
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=1263399295-19453-1-git-send-email-vincent.hanquez@eu.citrix.com \
--to=vincent.hanquez@eu.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).