From: Markus Armbruster <armbru@redhat.com>
To: dongxingshui <opensource.dxs@aliyun.com>
Cc: zhongguocheng@huawei.com, dongxingshui@huawei.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Avoid memory leak
Date: Thu, 26 Nov 2015 08:40:24 +0100 [thread overview]
Message-ID: <87mvu1mcnr.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <1448501448-5652-1-git-send-email-opensource.dxs@aliyun.com> (dongxingshui's message of "Thu, 26 Nov 2015 01:30:48 +0000")
dongxingshui <opensource.dxs@aliyun.com> writes:
> monitor.c: Avoid memory leak
>
> When send a wrong qmp command, a memory leak occurs. Fix it.
>
> Signed-off-by: dongxingshui <opensource.dxs@aliyun.com>
Functionally the same as
http://lists.gnu.org/archive/html/qemu-devel/2015-10/msg06862.html
Message-Id: <1446117309-15322-1-git-send-email-armbru@redhat.com>
The delay getting that merged is entirely my fault. Thanks!
prev parent reply other threads:[~2015-11-26 7:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 1:30 [Qemu-devel] [PATCH] Avoid memory leak dongxingshui
2015-11-26 3:43 ` [Qemu-devel] [PATCH for-2.5] " Eric Blake
2015-11-26 8:38 ` stefano
2015-11-26 8:52 ` Markus Armbruster
2015-11-26 7:40 ` Markus Armbruster [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=87mvu1mcnr.fsf@blackfin.pond.sub.org \
--to=armbru@redhat.com \
--cc=dongxingshui@huawei.com \
--cc=opensource.dxs@aliyun.com \
--cc=qemu-devel@nongnu.org \
--cc=zhongguocheng@huawei.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 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.