From: Eric Blake <eblake@redhat.com>
To: sathnaga@linux.vnet.ibm.com, qemu-devel@nongnu.org
Cc: Viktor Mihajlovski <mihajlov@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH for-2.12] hmp.c: Revert hmp_info_cpus output format
Date: Tue, 27 Mar 2018 08:59:04 -0500 [thread overview]
Message-ID: <686b98e4-cf4e-00c9-e4fd-a3efd9f52994@redhat.com> (raw)
In-Reply-To: <20180327123800.28851-1-sathnaga@linux.vnet.ibm.com>
On 03/27/2018 07:38 AM, sathnaga@linux.vnet.ibm.com wrote:
> From: Satheesh Rajendran <sathnaga@linux.vnet.ibm.com>
>
> This commit 137b5cb6ab565cb3781d5337591e155932b4230e
> refactors info cpus output and changes output format from
> 'thread_id' to 'thread-id', this would break parsing
> of output in above layers like libvirt, test framework etc.
>
> This patch just reverts back output format to 'thread_id'.
>
> CC: Viktor Mihajlovski <mihajlov@linux.vnet.ibm.com>
> Signed-off-by: Satheesh Rajendran <sathnaga@linux.vnet.ibm.com>
> ---
> hmp.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
I'm not opposed to this patch (because it is a trivial way to keep older
stuff working), but agree with Daniel that HMP output can change at any
time, so other stuff relying on HMP should be fixed. Libvirt is not
affected, so if we DO take this into 2.12, we should update the commit
message to drop mention of libvirt being impacted, maybe along the lines of:
Commit 137b5cb6 refactored 'info cpus' output, changing 'thread_id' to
'thread-id'. While HMP is not a stable interface, it is trivial to keep
the spelling consistent for test frameworks that have not yet updated to
using QMP.
With the improved commit message,
Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2018-03-27 13:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 12:38 [Qemu-devel] [PATCH] hmp.c: Revert hmp_info_cpus output format sathnaga
2018-03-27 12:40 ` Daniel P. Berrangé
[not found] ` <20180327131619.GA27591@localhost.localdomain>
2018-03-27 13:20 ` Daniel P. Berrangé
2018-03-27 13:39 ` satheesh rajendran
2018-03-27 13:24 ` satheesh rajendran
2018-03-27 13:59 ` Eric Blake [this message]
2018-03-27 14:25 ` [Qemu-devel] [PATCH for-2.12] " Cornelia Huck
2018-03-27 15:32 ` Viktor Mihajlovski
2018-03-27 14:03 ` [Qemu-devel] [PATCH] " Eric Blake
2018-03-27 14:04 ` Dr. David Alan Gilbert
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=686b98e4-cf4e-00c9-e4fd-a3efd9f52994@redhat.com \
--to=eblake@redhat.com \
--cc=mihajlov@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=sathnaga@linux.vnet.ibm.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 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).