From: Olaf Hering <olaf@aepfle.de>
To: Zhigang Wang <zhigang.x.wang@oracle.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] tools/hotplug/Linux/block: fix shared loop device detection
Date: Thu, 7 Jul 2011 10:19:12 +0200 [thread overview]
Message-ID: <20110707081912.GA25334@aepfle.de> (raw)
In-Reply-To: <52449dfa903562aa563f.1309991973@zhigang.us.oracle.com>
On Wed, Jul 06, Zhigang Wang wrote:
> # HG changeset patch
> # User Zhigang Wang <zhigang.x.wang@oracle.com>
> # Date 1309991886 14400
> # Node ID 52449dfa903562aa563fef0d229e2dc61a768f4c
> # Parent 2f63562df1c4230492a81793dce3672f93c93d9a
> tools/hotplug/Linux/block: fix shared loop device detection
>
> We need to prefix 0 or more '0' to '$dev':
>
> # stat -c '%D' "/system.img"
> 13
> # losetup -a
> /dev/loop0: [0013]:12062248 (/system.img)
>
> Signed-off-by: Zhigang Wang <zhigang.x.wang@oracle.com>
The leading zero was in the 4.0 code. Thanks for spotting.
Acked-by: Olaf Hering <olaf@aepfle.de>
Olaf
next prev parent reply other threads:[~2011-07-07 8:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 22:39 [PATCH] tools/hotplug/Linux/block: fix shared loop device detection Zhigang Wang
2011-07-07 8:19 ` Olaf Hering [this message]
2011-07-08 17:12 ` Ian Jackson
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=20110707081912.GA25334@aepfle.de \
--to=olaf@aepfle.de \
--cc=xen-devel@lists.xensource.com \
--cc=zhigang.x.wang@oracle.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.