From: Gerd Hoffmann <kraxel@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3] fix info qtree indention
Date: Wed, 15 Aug 2012 10:26:07 +0200 [thread overview]
Message-ID: <502B5D1F.3040709@redhat.com> (raw)
In-Reply-To: <1344320840-17228-1-git-send-email-kraxel@redhat.com>
On 08/07/12 08:27, Gerd Hoffmann wrote:
> Without the patch bus properties are are not in line with the other
> properties:
>
> [ ... ]
> dev: fw_cfg, id ""
> ctl_iobase = 0x510
> data_iobase = 0x511
> irq 0
> mmio ffffffffffffffff/0000000000000002
> mmio ffffffffffffffff/0000000000000001
> [ ... ]
>
> With the patch applied everything is lined up properly:
>
> [ ... ]
> dev: fw_cfg, id ""
> ctl_iobase = 0x510
> data_iobase = 0x511
> irq 0
> mmio ffffffffffffffff/0000000000000002
> mmio ffffffffffffffff/0000000000000001
> [ ... ]
>
> Needed to make the autotest qtree parser happy.
Ping?
cheers,
Gerd
next prev parent reply other threads:[~2012-08-15 8:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 6:27 [Qemu-devel] [PATCH v3] fix info qtree indention Gerd Hoffmann
2012-08-15 8:26 ` Gerd Hoffmann [this message]
2012-08-24 6:11 ` 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=502B5D1F.3040709@redhat.com \
--to=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).