From: "Andreas Färber" <afaerber@suse.de>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: peter.maydell@linaro.org, armbru@redhat.com, pbonzini@redhat.com,
lcapitulino@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC 0/4] QOM class properties - do we need them?
Date: Thu, 29 Sep 2016 12:16:48 +0200 [thread overview]
Message-ID: <02de8b86-6c44-5c5a-0498-fe60fb95b48c@suse.de> (raw)
In-Reply-To: <1475108205-6043-1-git-send-email-david@gibson.dropbear.id.au>
Am 29.09.2016 um 02:16 schrieb David Gibson:
> is there really any value to supporting the "class"
> properties in addition to the "instance" properties?
Yes, it makes enumerating available properties easier by not requiring
to instantiate a new instance for printing, e.g., ",help" information.
Regards,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2016-09-29 10:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-29 0:16 [Qemu-devel] [RFC 0/4] QOM class properties - do we need them? David Gibson
2016-09-29 0:16 ` [Qemu-devel] [RFC 1/4] qcrypto: Remove usage of class properties David Gibson
2016-09-29 0:16 ` [Qemu-devel] [RFC 2/4] s390: Don't use " David Gibson
2016-09-29 0:16 ` [Qemu-devel] [RFC 3/4] tests: Remove tests for " David Gibson
2016-09-29 0:16 ` [Qemu-devel] [RFC 4/4] qom: Abolish " David Gibson
2016-09-29 7:52 ` [Qemu-devel] [RFC 0/4] QOM class properties - do we need them? Paolo Bonzini
2016-09-29 8:14 ` Daniel P. Berrange
2016-09-29 10:12 ` Andreas Färber
2016-09-29 10:21 ` Daniel P. Berrange
2016-09-29 10:23 ` Andreas Färber
2016-09-29 23:36 ` David Gibson
2016-10-04 9:51 ` Kevin Wolf
2016-09-29 23:33 ` David Gibson
2016-09-30 8:06 ` Daniel P. Berrange
2016-09-29 10:16 ` Andreas Färber [this message]
2016-09-29 23:37 ` David Gibson
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=02de8b86-6c44-5c5a-0498-fe60fb95b48c@suse.de \
--to=afaerber@suse.de \
--cc=armbru@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=lcapitulino@redhat.com \
--cc=pbonzini@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.