From: Kevin Wolf <kwolf@redhat.com>
To: Bruce Rogers <brogers@novell.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] use qemu_free() instead of free()
Date: Fri, 14 May 2010 13:44:22 +0200 [thread overview]
Message-ID: <4BED3796.5000108@redhat.com> (raw)
In-Reply-To: <4BEC175902000048000957DF@sinclair.provo.novell.com>
Am 13.05.2010 23:14, schrieb Bruce Rogers:
> There is a call to free() where qemu_free() should instead be used.
>
> Signed-off-by: Bruce Rogers <brogers@novell.com>
>
> diff --git a/block.c b/block.c
> index 48305b7..1a9d72d 100644
> --- a/block.c
> +++ b/block.c
> @@ -2073,7 +2073,7 @@ int bdrv_aio_multiwrite(BlockDriverState *bs, BlockRequest
> *reqs, int num_reqs)
> return 0;
>
> fail:
> - free(mcb);
> + qemu_free(mcb);
> return -1;
> }
Fixed the line wrap and applied to the block branch. Thanks.
Kevin
prev parent reply other threads:[~2010-05-14 11:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 21:14 [Qemu-devel] [PATCH] use qemu_free() instead of free() Bruce Rogers
2010-05-14 11:44 ` Kevin Wolf [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=4BED3796.5000108@redhat.com \
--to=kwolf@redhat.com \
--cc=brogers@novell.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).