From: Zhigang Wang <zhigang.x.wang@oracle.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: [PATCH]Remove XendLogging dependency from xen/utils/blkif.py
Date: Wed, 21 May 2008 17:11:47 +0800 [thread overview]
Message-ID: <4833E753.9080708@oracle.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 374 bytes --]
hi,
xen/utils/blkif.py imported log from xen.xend.XendLogging but never uses.
Other tools rather than xend can easily get the block device id by calling
blkdev_name_to_number(). So it's useful to other tools.
But the dependency on XendLogging prevents it from directly resuing.
This patch removes the dependency on XendLogging from xen/utils/blkif.py.
thanks,
zhigang
[-- Attachment #2: xen-blkif-logging.patch --]
[-- Type: text/x-patch, Size: 789 bytes --]
Remove XendLogging dependency from xen/utils/blkif.py
xen/utils/blkif.py imported log from xen.xend.XendLogging but never uses.
Other tools rather than xend can easily get the block device id by calling
blkdev_name_to_number(). So it's useful to other tools.
But the dependency on XendLogging prevents it from directly resuable.
This patch removes the dependency on XendLogging from xen/utils/blkif.py.
Signed-off-by: Zhigang Wang <zhigang.x.wang@oracle.com>
--- xen-unstable.orig/tools/python/xen/util/blkif.py 2008-05-12 16:43:51.000000000 +0800
+++ xen-unstable/tools/python/xen/util/blkif.py 2008-05-21 16:55:06.000000000 +0800
@@ -2,8 +2,6 @@
import re
import string
-from xen.xend.XendLogging import log
-
def expand_dev_name(name):
if not name:
return name
[-- 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:[~2008-05-21 9:11 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=4833E753.9080708@oracle.com \
--to=zhigang.x.wang@oracle.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.