qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Eric Blake <eblake@redhat.com>,
	Alexey Kardashevskiy <aik@ozlabs.ru>,
	qemu-devel@nongnu.org
Cc: Markus Armbruster <armbru@redhat.com>,
	Andrea Bolognani <abologna@redhat.com>
Subject: Re: [Qemu-devel] [PATCH qemu v4 1/2] qmp: Merge ObjectPropertyInfo and DevicePropertyInfo
Date: Mon, 30 Apr 2018 12:04:55 +0200	[thread overview]
Message-ID: <fe645105-209e-6ba1-5661-d475cb74f3a8@redhat.com> (raw)
In-Reply-To: <f3b6cbb3-4484-55cf-3529-ce1a9946904f@redhat.com>

On 18/04/2018 18:35, Eric Blake wrote:
> On 03/02/2018 06:25 PM, Alexey Kardashevskiy wrote:
>> ObjectPropertyInfo is more generic and only missing @description.
>> This adds a description to ObjectPropertyInfo and removes
>> DevicePropertyInfo so the resulting ObjectPropertyInfo can be used
>> elsewhere.
>>
>> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
>> ---
>> Changes:
>> v4:
>> * added (since 2.12) to the new field
> 
> And since it missed 2.12,

It is in 2.12:

commit 961c47bb8bacc9ae21c0760fa6e2594156299dd7
Author: Alexey Kardashevskiy <aik@ozlabs.ru>
Date:   Fri Mar 2 00:09:39 2018 +1100

    qmp: Add qom-list-properties to list QOM object properties
    
    There is already 'device-list-properties' which does most of the job,
    however it does not handle everything returned by qom-list-types such
    as machines as they inherit directly from TYPE_OBJECT and not TYPE_DEVICE.
    It does not handle abstract classes either.
    
    This adds a new qom-list-properties command which prints properties
    of a specific class and its instance. It is pretty much a simplified copy
    of the device-list-properties handler.
    
    Since it creates an object instance, device properties should appear
    in the output as they are copied to QOM properties at the instance_init
    hook.
    
    This adds a object_class_property_iter_init() helper to allow class
    properties enumeration uses it in the new QMP command to allow properties
    listing for abstract classes.
    
    Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
    Message-Id: <20180301130939.15875-3-aik@ozlabs.ru>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

commit 35f63767dc77d85bebff6c6565aceaf74023776a
Author: Alexey Kardashevskiy <aik@ozlabs.ru>
Date:   Fri Mar 2 00:09:38 2018 +1100

    qmp: Merge ObjectPropertyInfo and DevicePropertyInfo
    
    ObjectPropertyInfo is more generic and only missing @description.
    This adds a description to ObjectPropertyInfo and removes
    DevicePropertyInfo so the resulting ObjectPropertyInfo can be used
    elsewhere.
    
    Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
    Message-Id: <20180301130939.15875-2-aik@ozlabs.ru>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

Thanks,

Paolo

>> * removed wrong reindents
>> ---
>>  qapi-schema.json | 23 +++++------------------
>>  qdev-monitor.c   |  6 +++---
>>  qmp.c            | 14 +++++++-------
>>  3 files changed, 15 insertions(+), 28 deletions(-)
>>
>> diff --git a/qapi-schema.json b/qapi-schema.json
>> index 0262b9f..5cdf89a 100644
>> --- a/qapi-schema.json
>> +++ b/qapi-schema.json
>> @@ -1266,10 +1266,12 @@
>>  #        3) A link type in the form 'link<subtype>' where subtype is a qdev
>>  #           device type name.  Link properties form the device model graph.
>>  #
>> +# @description: if specified, the description of the property (since 2.12).
> 
> this should be tweaked to say since 2.13.
> 
> 

  reply	other threads:[~2018-04-30 10:05 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-03  0:25 [Qemu-devel] [PATCH qemu v4 0/2] qmp: Add qom-list-properties to list QOM object properties Alexey Kardashevskiy
2018-03-03  0:25 ` [Qemu-devel] [PATCH qemu v4 1/2] qmp: Merge ObjectPropertyInfo and DevicePropertyInfo Alexey Kardashevskiy
2018-04-18 16:35   ` Eric Blake
2018-04-30 10:04     ` Paolo Bonzini [this message]
2018-03-03  0:25 ` [Qemu-devel] [PATCH qemu v4 2/2] qmp: Add qom-list-properties to list QOM object properties Alexey Kardashevskiy
2018-04-13 14:16   ` Markus Armbruster
2018-04-30  6:52     ` [Qemu-devel] [PATCH qemu] qom: Document qom/device-list-properties implementation specific Alexey Kardashevskiy
2018-04-30  6:56       ` no-reply
2018-04-30  7:07         ` Alexey Kardashevskiy
2018-04-30  6:58       ` no-reply
2018-04-30  7:00       ` no-reply
2018-04-30  9:39       ` Paolo Bonzini
2018-05-02  1:26         ` Alexey Kardashevskiy
2018-05-02  6:34           ` Markus Armbruster
2018-05-02  9:11             ` Paolo Bonzini
2018-05-02  9:33               ` Alexey Kardashevskiy
2018-05-02  9:50                 ` Paolo Bonzini
2018-05-03  6:22                   ` Alexey Kardashevskiy
2018-05-03 10:54                     ` Paolo Bonzini
2018-05-02  9:38               ` Markus Armbruster
2018-05-02  9:47                 ` Paolo Bonzini
2018-05-02 12:36                   ` Markus Armbruster
2018-05-02 12:42                     ` Paolo Bonzini
2018-05-02 13:31                       ` Markus Armbruster
2018-05-02 13:32                         ` Paolo Bonzini
2018-05-01 13:01       ` Eric Blake
2018-05-02  1:33         ` Alexey Kardashevskiy

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=fe645105-209e-6ba1-5661-d475cb74f3a8@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=abologna@redhat.com \
    --cc=aik@ozlabs.ru \
    --cc=armbru@redhat.com \
    --cc=eblake@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).