From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>, "Denis V. Lunev" <den@openvz.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
qemu-devel@nongnu.org, Pavel Butsykin <pbutsykin@virtuozzo.com>
Subject: Re: [Qemu-devel] [PATCH 1/4] hmp-commands-info: move info_cmds content out of monitor.c
Date: Fri, 18 Sep 2015 17:20:12 +0200 [thread overview]
Message-ID: <55FC2BAC.6040402@redhat.com> (raw)
In-Reply-To: <87h9mrrcbf.fsf@blackfin.pond.sub.org>
On 18/09/2015 17:12, Markus Armbruster wrote:
> "Denis V. Lunev" <den@openvz.org> writes:
>
>> From: Pavel Butsykin <pbutsykin@virtuozzo.com>
>>
>> For moving target- and device-specific code from monitor.c,
>> to beginning we move info_cmds content to hmp-commands-info.hx
>>
>> Signed-off-by: Pavel Butsykin <pbutsykin@virtuozzo.com>
>> Signed-off-by: Denis V. Lunev <den@openvz.org>
>> CC: Paolo Bonzini <pbonzini@redhat.com>
>> CC: Peter Maydell <peter.maydell@linaro.org>
>
> For me, this commit drops "info pci".
>
> Before:
>
> $ qemu-system-x86_64 -nodefaults -S -display none -monitor stdio
> QEMU 2.4.50 monitor - type 'help' for more information
> (qemu) info pci
> Bus 0, device 0, function 0:
> Host bridge: PCI device 8086:1237
> id ""
> Bus 0, device 1, function 0:
> ISA bridge: PCI device 8086:7000
> id ""
> Bus 0, device 1, function 1:
> IDE controller: PCI device 8086:7010
> BAR4: I/O at 0xffffffffffffffff [0x000e].
> id ""
> Bus 0, device 1, function 3:
> Bridge: PCI device 8086:7113
> IRQ 0.
> id ""
>
> After:
>
> (qemu) info pci
> unknown command: 'pci'
>
> Please advise.
s/advise/fix/... patch sent. Let me know who shall send it to Peter.
(BTW, it's obvious that I don't scale to 100+ patches per month. Do you
still have that script of yours looking for unmaintained areas?).
Paolo
next prev parent reply other threads:[~2015-09-18 15:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-10 15:38 [Qemu-devel] [PATCH v4 0/4] Move target- and device specific code from monitor Denis V. Lunev
2015-09-10 15:38 ` [Qemu-devel] [PATCH 1/4] hmp-commands-info: move info_cmds content out of monitor.c Denis V. Lunev
2015-09-18 15:12 ` Markus Armbruster
2015-09-18 15:20 ` Paolo Bonzini [this message]
2015-09-22 8:38 ` Markus Armbruster
2015-09-18 16:06 ` [Qemu-devel] [PATCH] hmp-commands-info.hx: fix drops hmp "info pci" Pavel Butsykin
2015-09-18 16:26 ` Eric Blake
2015-09-18 16:57 ` Pavel Butsykin
2015-09-21 5:58 ` Markus Armbruster
2015-09-21 9:32 ` Paolo Bonzini
2015-09-21 14:07 ` Markus Armbruster
2015-09-10 15:38 ` [Qemu-devel] [PATCH 2/4] monitor: remove target-specific code from monitor.c Denis V. Lunev
2015-09-10 15:39 ` [Qemu-devel] [PATCH 3/4] hmp-commands.hx: fix end of table info Denis V. Lunev
2015-09-10 15:39 ` [Qemu-devel] [PATCH 4/4] monitor: added generation of documentation for hmp-commands-info.hx Denis V. Lunev
2015-09-10 16:18 ` [Qemu-devel] [PATCH v4 0/4] Move target- and device specific code from monitor Peter Crosthwaite
2015-09-10 16:22 ` Paolo Bonzini
2015-09-10 16:26 ` Denis V. Lunev
-- strict thread matches above, loose matches on Subject: below --
2015-09-08 7:09 [Qemu-devel] [PATCH v3 " Denis V. Lunev
2015-09-08 7:09 ` [Qemu-devel] [PATCH 1/4] hmp-commands-info: move info_cmds content out of monitor.c Denis V. Lunev
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=55FC2BAC.6040402@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=den@openvz.org \
--cc=pbutsykin@virtuozzo.com \
--cc=peter.maydell@linaro.org \
--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).