qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>,
	Viktor Mihajlovski <mihajlov@linux.vnet.ibm.com>
Cc: agraf@suse.de, ehabkost@redhat.com, david@redhat.com,
	qemu-devel@nongnu.org, armbru@redhat.com, dgilbert@redhat.com,
	borntraeger@de.ibm.com, qemu-s390x@nongnu.org,
	pbonzini@redhat.com, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCHv2 0/3] add query-cpu-fast and related s390 changes
Date: Wed, 14 Feb 2018 14:01:21 -0600	[thread overview]
Message-ID: <cc093bbf-9470-d9ab-4390-5e93f33c13fb@redhat.com> (raw)
In-Reply-To: <a6135d66-6673-a49d-01fa-9fa4d55b3aa1@redhat.com>

On 02/14/2018 09:16 AM, Eric Blake wrote:
>> How shall we proceed with this series? Patch 3 depends upon patch 1, so
>> I think it makes sense to merge this in one go.
>>
>> I can give my R-b on patch 1 and Someone(tm) can merge this, or I can
>> take the whole series through the s390 tree (with some further
>> reviews/acks on patches 2/3).
> 
> I'd still like to give a thorough QMP review; it's on my list to get to 
> today.

Okay, I've added more review comments; I think there's still enough 
worth polishing that resending a v3 of the series is worthwhile, and do 
agree that we want all three patches through a single tree (s390 sound 
fine to me).  But in general, I'm okay with the QMP changes (what looks 
like duplication is caused by modernizing the naming, which means we 
DON'T want to play games with trying to inherit one type from the other, 
and the argument about deprecating the old naming seems reasonable).

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org

      parent reply	other threads:[~2018-02-14 20:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-13 17:18 [Qemu-devel] [PATCHv2 0/3] add query-cpu-fast and related s390 changes Viktor Mihajlovski
2018-02-13 17:18 ` [Qemu-devel] [PATCHv2 1/3] qmp: expose s390-specific CPU info Viktor Mihajlovski
2018-02-14  9:30   ` Christian Borntraeger
2018-02-14  9:46   ` David Hildenbrand
2018-02-13 17:18 ` [Qemu-devel] [PATCHv2 2/3] qmp: add query-cpus-fast Viktor Mihajlovski
2018-02-14 10:11   ` Cornelia Huck
2018-02-14 19:46   ` Eric Blake
2018-02-13 17:18 ` [Qemu-devel] [PATCHv2 3/3] qmp: add architecture specific cpu data for query-cpus-fast Viktor Mihajlovski
2018-02-14 10:15   ` Cornelia Huck
2018-02-14 15:15     ` Eric Blake
2018-02-14 15:27       ` Cornelia Huck
2018-02-14 15:50         ` Viktor Mihajlovski
2018-02-14 16:07           ` Eric Blake
2018-02-14 19:56   ` Eric Blake
2018-02-14 10:57 ` [Qemu-devel] [PATCHv2 0/3] add query-cpu-fast and related s390 changes Cornelia Huck
2018-02-14 14:00   ` Viktor Mihajlovski
2018-02-14 15:49     ` Dr. David Alan Gilbert
2018-02-14 15:16   ` Eric Blake
2018-02-14 15:26     ` Cornelia Huck
2018-02-14 20:01     ` Eric Blake [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=cc093bbf-9470-d9ab-4390-5e93f33c13fb@redhat.com \
    --to=eblake@redhat.com \
    --cc=agraf@suse.de \
    --cc=armbru@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=david@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=mihajlov@linux.vnet.ibm.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=rth@twiddle.net \
    /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).