From: Jim Fehlig <jfehlig@novell.com>
To: xen-devel@lists.xensource.com
Subject: [PATCH][xenapi] Fix console methods that use undefined variables
Date: Tue, 24 Jul 2007 19:00:14 -0600 [thread overview]
Message-ID: <46A6A09E.3070403@novell.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 79 bytes --]
A few of the console methods were using xendom when not defined.
Regards,
Jim
[-- Attachment #2: xend_console_undefined.patch --]
[-- Type: text/x-patch, Size: 1248 bytes --]
# HG changeset patch
# User Jim Fehlig <jfehlig@novell.com>
# Date 1185324782 21600
# Node ID 5a9efcada31c6c28457c7c6c68dd3d1ad712519b
# Parent 1f348e70a5affdea9b44c1e39cd5ef094ad4a0bf
Fix Xen API console methods that use undefined variables.
Signed-off-by: Jim Fehlig <jfehlig@novell.com>
diff -r 1f348e70a5af -r 5a9efcada31c tools/python/xen/xend/XendAPI.py
--- a/tools/python/xen/xend/XendAPI.py Tue Jul 10 11:10:38 2007 +0100
+++ b/tools/python/xen/xend/XendAPI.py Tue Jul 24 18:53:02 2007 -0600
@@ -2357,11 +2357,13 @@ class XendAPI(object):
return xen_api_success(cons)
def console_get_location(self, session, console_ref):
+ xendom = XendDomain.instance()
return xen_api_success(xendom.get_dev_property_by_uuid('console',
console_ref,
'location'))
def console_get_protocol(self, session, console_ref):
+ xendom = XendDomain.instance()
return xen_api_success(xendom.get_dev_property_by_uuid('console',
console_ref,
'protocol'))
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
reply other threads:[~2007-07-25 1:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=46A6A09E.3070403@novell.com \
--to=jfehlig@novell.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.