From: "Daniel P. Berrange" <berrange@redhat.com>
To: Gerd Hoffmann <kraxel@suse.de>
Cc: xen-devel@lists.xensource.com
Subject: Re: [patch] Add more xc_error_code values.
Date: Fri, 8 Dec 2006 15:35:26 +0000 [thread overview]
Message-ID: <20061208153526.GB7372@redhat.com> (raw)
In-Reply-To: <20061208150949.320661000@suse.de>
On Fri, Dec 08, 2006 at 04:09:58PM +0100, Gerd Hoffmann wrote:
> XC_INVALID_PARAM
> such as asking for features unsupported by either xen or guest kernel.
> XC_OUT_OF_MEMORY
> no comment ;)
>
> Signed-off-by: Gerd Hoffmann <kraxel@suse.de>
> ---
> tools/libxc/xenctrl.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> Index: build-32-unstable-12802/tools/libxc/xenctrl.h
> ===================================================================
> --- build-32-unstable-12802.orig/tools/libxc/xenctrl.h
> +++ build-32-unstable-12802/tools/libxc/xenctrl.h
> @@ -687,6 +687,8 @@ typedef enum {
> XC_ERROR_NONE = 0,
> XC_INTERNAL_ERROR = 1,
> XC_INVALID_KERNEL = 2,
> + XC_INVALID_PARAM = 3,
> + XC_OUT_OF_MEMORY = 4,
> } xc_error_code;
You'll also want to add matching user friendly descriptions to the method
xc_error_code_to_description in tools/libxc/xc_private.c otherwise they'll
just get converted into 'Unknown error code'. I thought I had a comment
to this effect just before the declaration of xc_error_code enum, but looks
like I mislaid it.
Regards,
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
next prev parent reply other threads:[~2006-12-08 15:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-08 15:09 [patch] Add more xc_error_code values Gerd Hoffmann
2006-12-08 15:35 ` Daniel P. Berrange [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-12-08 16:16 Gerd Hoffmann
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=20061208153526.GB7372@redhat.com \
--to=berrange@redhat.com \
--cc=kraxel@suse.de \
--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.