From: Alexander Barabash <alexander_barabash@mentor.com>
Date: Tue, 21 Feb 2012 10:14:22 +0000 (+0200)
Subject: qom: Document ways to retrieve child object added by object_property_add_child()
X-Git-Tag: TizenStudio_2.0_p2.3.2~208^2~4494
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=358b54654aa85f97402aca4be3b1a7b7d08bab70;p=sdk%2Femulator%2Fqemu.git

qom: Document ways to retrieve child object added by object_property_add_child()

object_property_add_child() creates a property whose values as a string is
the child object's canonical path.

Acked-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Alexander Barabash <alexander_barabash@mentor.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
---

diff --git a/include/qemu/object.h b/include/qemu/object.h
index ff6be14..69e4b7b 100644
--- a/include/qemu/object.h
+++ b/include/qemu/object.h
@@ -837,6 +837,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);