From: Stefan Hajnoczi <stefanha@gmail.com>
To: Stefan Berger <stefanb@linux.vnet.ibm.com>
Cc: qemu-trivial@nongnu.org, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v3] Fix some memory leaks in test-visitor-serialization
Date: Thu, 28 Mar 2013 16:29:16 +0100 [thread overview]
Message-ID: <20130328152916.GA31205@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1364483920.28637.3.camel@d941e-10>
On Thu, Mar 28, 2013 at 11:18:40AM -0400, Stefan Berger wrote:
> This patch fixes some of the memory leaks in test-visitor-serialization but not all of them.
>
> Signed-off-by: Stefan Berger <stefanb@linux.vnet.ibm.com>
>
> ---
> v2->v3: repost
>
> v1->v2: call qobject_decref(obj) earlier
>
> ---
> tests/test-visitor-serialization.c | 12 +++++++++++-
> 1 file changed, 11 insertions(+), 1 deletion(-)
Thanks, applied to the trivial patches -next tree:
https://github.com/stefanha/qemu/commits/trivial-patches-next
Stefan
next prev parent reply other threads:[~2013-03-28 15:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 15:18 [Qemu-devel] [PATCH v3] Fix some memory leaks in test-visitor-serialization Stefan Berger
2013-03-28 15:29 ` Stefan Hajnoczi [this message]
2013-03-28 16:28 ` Stefan Berger
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=20130328152916.GA31205@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=stefanb@linux.vnet.ibm.com \
/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).