From: Igor Mammedov <imammedo@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
qemu-devel@nongnu.org, "Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH] fixup! qom: Fix ambiguous path detection when ambiguous=NULL
Date: Mon, 10 Jul 2017 18:26:36 +0200 [thread overview]
Message-ID: <20170710182636.3269e9d8@nial.brq.redhat.com> (raw)
In-Reply-To: <20170710153331.GC5167@localhost.localdomain>
On Mon, 10 Jul 2017 12:33:31 -0300
Eduardo Habkost <ehabkost@redhat.com> wrote:
> On Mon, Jul 10, 2017 at 11:45:57AM -0300, Eduardo Habkost wrote:
> > On Mon, Jul 10, 2017 at 10:10:41AM +0200, Igor Mammedov wrote:
> > > On Fri, 7 Jul 2017 18:30:51 -0300
> > > Eduardo Habkost <ehabkost@redhat.com> wrote:
> [...]
> > > > +
> > > > + object_unparent(obj1);
> > > > + object_unparent(obj2a);
> > > > + object_unparent(obj2b);
> > > Are above unparenting is necessary?
> > >
> > > > + object_unparent(cont1);
> > > Wouldn't parent destruction sufficient to trigger
> > > implicit destruction of children?
> >
> > Probably it is. I will test it.
>
> The obj1 and obj2a object_unparent() calls are really
> unnecessary. object_unparent(obj2b) is still necessary because
> it is attached direcly to root.
>
> Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
> ---
> tests/check-qom-proplist.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/tests/check-qom-proplist.c b/tests/check-qom-proplist.c
> index 381532c..432b665 100644
> --- a/tests/check-qom-proplist.c
> +++ b/tests/check-qom-proplist.c
> @@ -605,8 +605,6 @@ static void test_qom_partial_path(void)
> g_assert(!ambiguous);
> g_assert(object_resolve_path("obj1", NULL) == obj1);
>
> - object_unparent(obj1);
> - object_unparent(obj2a);
> object_unparent(obj2b);
> object_unparent(cont1);
> }
next prev parent reply other threads:[~2017-07-10 16:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-07 21:30 [Qemu-devel] [PATCH 0/2] qom: Fix ambiguous path detection when ambiguous=NULL Eduardo Habkost
2017-07-07 21:30 ` [Qemu-devel] [PATCH 1/2] tests: Test case for object_resolve_path*() Eduardo Habkost
2017-07-10 8:10 ` Igor Mammedov
2017-07-10 14:45 ` Eduardo Habkost
2017-07-10 14:48 ` Igor Mammedov
2017-07-10 15:33 ` [Qemu-devel] [PATCH] fixup! qom: Fix ambiguous path detection when ambiguous=NULL Eduardo Habkost
2017-07-10 16:26 ` Igor Mammedov [this message]
2017-07-07 21:30 ` [Qemu-devel] [PATCH 2/2] " Eduardo Habkost
2017-07-10 8:18 ` Igor Mammedov
2017-07-10 6:42 ` [Qemu-devel] [PATCH 0/2] " Mark Cave-Ayland
2017-07-10 18:23 ` Eduardo Habkost
2017-07-13 12:09 ` Paolo Bonzini
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=20170710182636.3269e9d8@nial.brq.redhat.com \
--to=imammedo@redhat.com \
--cc=afaerber@suse.de \
--cc=ehabkost@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).