From: Chris Lalancette <clalance@redhat.com>
To: "YuLin @ wr" <yulin724@gmail.com>
Cc: "Xu, Dongxiao" <dongxiao.xu@intel.com>,
xen-devel@lists.xensource.com,
Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: [PATCH] Fix the return value of blkdev_name_to_number
Date: Mon, 30 Jun 2008 15:10:03 +0200 [thread overview]
Message-ID: <4868DB2B.2060100@redhat.com> (raw)
In-Reply-To: <8eeed7950806300549w628f4889n20ac3f352196df37@mail.gmail.com>
YuLin @ wr wrote:
> hi,
>
> Maybe you should list the position where there is a problem of "unpack
> non-sequence" about blkdev_name_to_number
> I only found some usages of blkdev_name_to_number which only accept one
> return value, and the left value is not a tuple apparently.
Yes, sorry about that. I posted a patch earlier today which should fix the rest
of the blkdev_name_to_number fixes, and between that and the other os.stat()
fix, hopefully that should fix it up.
Chris Lalancette
prev parent reply other threads:[~2008-06-30 13:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-30 9:13 [PATCH] Fix the return value of blkdev_name_to_number Xu, Dongxiao
2008-06-30 12:49 ` YuLin @ wr
2008-06-30 13:10 ` Chris Lalancette [this message]
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=4868DB2B.2060100@redhat.com \
--to=clalance@redhat.com \
--cc=dongxiao.xu@intel.com \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
--cc=yulin724@gmail.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.