From: Anthony Liguori <anthony@codemonkey.ws>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 00/18] qom: dynamic properties and composition tree (v2)
Date: Mon, 05 Dec 2011 10:38:37 -0600 [thread overview]
Message-ID: <4EDCF38D.70609@codemonkey.ws> (raw)
In-Reply-To: <4EDCF162.3010909@redhat.com>
On 12/05/2011 10:29 AM, Paolo Bonzini wrote:
> On 12/05/2011 05:13 PM, Anthony Liguori wrote:
>>
>>>> Maybe now is the right time to rename the legacy properties to all be
>>>> prefixed with qdev-? That way we don't need to introduce two different
>>>> types for a single property.
>>>
>>> Why do you need such a prefix?
>>
>> To avoid an all-at-once conversion. I don't want to break -device and
>> maintaining string properties make it quite a bit easier to support
>> -device.
>
> -device would use parse/print, not get/set. So it would still use the strings.
I don't want -device to have special knowledge of properties. I want it to set
the properties are strings. The property implementation is private to Object.
Regards,
Anthony Liguori
>
> Paolo
next prev parent reply other threads:[~2011-12-05 16:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-03 0:56 [Qemu-devel] [PATCH v2 00/18] qom: dynamic properties and composition tree (v2) Paolo Bonzini
2011-12-03 2:40 ` Anthony Liguori
2011-12-03 14:24 ` Paolo Bonzini
2011-12-03 21:34 ` Anthony Liguori
2011-12-04 21:01 ` Anthony Liguori
2011-12-05 9:52 ` Paolo Bonzini
2011-12-05 14:36 ` Anthony Liguori
2011-12-05 14:50 ` Peter Maydell
2011-12-05 15:04 ` Anthony Liguori
2011-12-05 15:33 ` Peter Maydell
2011-12-05 19:28 ` Anthony Liguori
2011-12-05 15:47 ` Paolo Bonzini
2011-12-05 16:13 ` Anthony Liguori
2011-12-05 16:29 ` Paolo Bonzini
2011-12-05 16:38 ` Anthony Liguori [this message]
2011-12-05 17:01 ` Paolo Bonzini
-- strict thread matches above, loose matches on Subject: below --
2011-12-02 20:20 Anthony Liguori
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=4EDCF38D.70609@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=pbonzini@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).