From: Eric Blake <eblake@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@redhat.com>, qemu-devel@nongnu.org
Cc: peterx@redhat.com
Subject: Re: [Qemu-devel] [PATCH] qmp-test: fix response leak
Date: Mon, 26 Mar 2018 16:57:10 -0500 [thread overview]
Message-ID: <33c617bd-88ee-3778-7059-0ef4a5f2a679@redhat.com> (raw)
In-Reply-To: <887d47b3-9243-4088-4449-f92f1f3c2302@redhat.com>
On 03/26/2018 01:33 PM, Eric Blake wrote:
> On 03/26/2018 12:20 PM, Marc-André Lureau wrote:
>> Apparently introduced in commit a4f90923b520f1dc0a768634877eb412e5052c26.
>>
>> Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
>> ---
>> tests/qmp-test.c | 1 +
>> 1 file changed, 1 insertion(+)
>
> Reviewed-by: Eric Blake <eblake@redhat.com>
>
> I'll queue this through my qapi tree, unless applying Peter's for-2.12
> patches fixes it differently.
Okay, it's needed, and I'm queuing it.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
prev parent reply other threads:[~2018-03-26 21:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 17:20 [Qemu-devel] [PATCH] qmp-test: fix response leak Marc-André Lureau
2018-03-26 18:33 ` Eric Blake
2018-03-26 21:57 ` Eric Blake [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=33c617bd-88ee-3778-7059-0ef4a5f2a679@redhat.com \
--to=eblake@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=peterx@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).