From: "Andreas Färber" <afaerber@suse.de>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v5 5/8] qom: add object_new_with_props / object_new_withpropv constructors
Date: Fri, 19 Jun 2015 18:43:57 +0200 [thread overview]
Message-ID: <558446CD.7010900@suse.de> (raw)
In-Reply-To: <55844081.10208@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1797 bytes --]
Am 19.06.2015 um 18:17 schrieb Eric Blake:
> On 06/19/2015 10:08 AM, Andreas Färber wrote:
>> Am 19.06.2015 um 18:04 schrieb Eric Blake:
>>> On 05/27/2015 09:07 AM, Daniel P. Berrange wrote:
>>>> It is reasonably common to want to create an object, set a
>>>> number of properties, register it in the hierarchy and then
>>>> mark it as complete (if a user creatable type). This requires
>>>> quite a lot of error prone, verbose, boilerplate code to achieve.
>>>>
>>>
>>>> /**
>>>> + * object_new_with_props:
>>>> + * @typename: The name of the type of the object to instantiate.
>>>> + * @parent: the parent object
>>>> + * @id: The unique ID of the object
>>>> + * @errp: pointer to error object
>>>> + * @...: list of property names and values
>>>> + *
>>>> + * This function will initialize a new object using heap allocated memory.
>>>> + * The returned object has a reference count of 1, and will be freed when
>>>> + * the last reference is dropped.
>>>> + *
>>>> + * The @id parameter will be used when registering the object as a
>>>> + * child of @parent in the objects composition tree.
>>>
>>> s/objects/object's/
>>
>> Actually I think /objects is meant, so looks okay to me?
>
> Then s,objects,/objects, :)
>
> Yes, that reads okay as well (and now you see why adding a character,
> whether / or ', makes a difference).
Erm, on second thoughts "object composition tree" is meant. :) The
parent is specified by the caller. And since that file always just talks
of "composition tree" except for one case where it says "QOM composition
tree", let's just adapt to that.
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton; HRB
21284 (AG Nürnberg)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-06-19 16:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 15:07 [Qemu-devel] [PATCH v5 0/8] qom: misc fixes & enhancements to support TLS work Daniel P. Berrange
2015-05-27 15:07 ` [Qemu-devel] [PATCH v5 1/8] backends: fix typename of 'policy' enum property in hostmem obj Daniel P. Berrange
2015-05-27 15:07 ` [Qemu-devel] [PATCH v5 2/8] doc: document user creatable object types in help text Daniel P. Berrange
2015-05-27 15:07 ` [Qemu-devel] [PATCH v5 3/8] vl: create (most) objects before creating chardev backends Daniel P. Berrange
2015-05-27 15:07 ` [Qemu-devel] [PATCH v5 4/8] qom: add helper method for getting user objects root Daniel P. Berrange
2015-06-19 16:41 ` Andreas Färber
2015-05-27 15:07 ` [Qemu-devel] [PATCH v5 5/8] qom: add object_new_with_props / object_new_withpropv constructors Daniel P. Berrange
2015-06-19 16:04 ` Eric Blake
2015-06-19 16:08 ` Andreas Färber
2015-06-19 16:17 ` Eric Blake
2015-06-19 16:43 ` Andreas Färber [this message]
2015-05-27 15:07 ` [Qemu-devel] [PATCH v5 6/8] qom: make enum string tables const-correct Daniel P. Berrange
2015-06-19 16:05 ` Eric Blake
2015-05-27 15:07 ` [Qemu-devel] [PATCH v5 7/8] qom: add a object_property_add_enum helper method Daniel P. Berrange
2015-06-19 16:12 ` Eric Blake
2015-06-19 16:26 ` Andreas Färber
2015-06-19 16:38 ` Eric Blake
2015-06-19 16:44 ` Andreas Färber
2015-05-27 15:07 ` [Qemu-devel] [PATCH v5 8/8] qom: don't pass string table to object_get_enum method Daniel P. Berrange
2015-06-19 15:15 ` Andreas Färber
2015-06-19 16:15 ` Eric Blake
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=558446CD.7010900@suse.de \
--to=afaerber@suse.de \
--cc=eblake@redhat.com \
--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).