From: Avi Kivity <avi@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qcow2: free old snapshots array upon creation of a new one
Date: Thu, 08 Jan 2009 15:52:14 +0200 [thread overview]
Message-ID: <4966050E.3010105@redhat.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0901071827160.7496@intel-tinevez-2-302>
Johannes Schindelin wrote:
> Hi,
>
> On Wed, 7 Jan 2009, Anthony Liguori wrote:
>
>
>> Uri Lublin wrote:
>>
>>> Don't leak memory
>>>
>>> Signed-off-by: Uri Lublin <uril@redhat.com>
>>> ---
>>> qemu/block-qcow2.c | 1 +
>>> 1 files changed, 1 insertions(+), 0 deletions(-)
>>>
>> Please don't send patches against kvm-userspace.
>>
>
> git am -p2 <mbox>
>
That doesn't test the patch against upstream qemu.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2009-01-08 13:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-05 0:52 [Qemu-devel] [PATCH] qcow2: free old snapshots array upon creation of a new one Uri Lublin
2009-01-07 16:54 ` Anthony Liguori
2009-01-07 17:27 ` Johannes Schindelin
2009-01-08 13:52 ` Avi Kivity [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=4966050E.3010105@redhat.com \
--to=avi@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).