From: Anthony Liguori <anthony@codemonkey.ws>
To: alexander_barabash@mentor.com
Cc: pbonzini@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qom: Document ways to retrieve child object added by object_property_add_child()
Date: Wed, 22 Feb 2012 12:51:05 -0600 [thread overview]
Message-ID: <4F453919.8050001@redhat.com> (raw)
In-Reply-To: <1329819262-4617-1-git-send-email-alexander_barabash@mentor.com>
On 02/21/2012 04:14 AM, alexander_barabash@mentor.com wrote:
> From: Alexander Barabash<alexander_barabash@mentor.com>
>
> object_property_add_child() creates a property whose values as a string is
> the child object's canonical path.
>
> Signed-off-by: Alexander Barabash<alexander_barabash@mentor.com>
Applied. Thanks.
Regards,
Anthony Liguori
> ---
> include/qemu/object.h | 4 ++++
> 1 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/include/qemu/object.h b/include/qemu/object.h
> index ba2409d..d9e9221 100644
> --- a/include/qemu/object.h
> +++ b/include/qemu/object.h
> @@ -808,6 +808,10 @@ Object *object_resolve_path_type(const char *path, const char *typename,
> *
> * There is no way for a child to determine what its parent is. It is not
> * a bidirectional relationship. This is by design.
> + *
> + * The value of a child property as a C string will be the child object's
> + * canonical path. It can be retrieved using object_property_get_str().
> + * The child object itself can be retrieved using object_property_get_link().
> */
> void object_property_add_child(Object *obj, const char *name,
> Object *child, struct Error **errp);
prev parent reply other threads:[~2012-02-22 18:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-21 10:14 [Qemu-devel] [PATCH] qom: Document ways to retrieve child object added by object_property_add_child() alexander_barabash
2012-02-21 10:16 ` Paolo Bonzini
2012-02-22 18:51 ` Anthony Liguori [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=4F453919.8050001@redhat.com \
--to=anthony@codemonkey.ws \
--cc=alexander_barabash@mentor.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 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.