From: Kevin Wolf <kwolf@redhat.com>
To: Dong Xu Wang <wdongxu@linux.vnet.ibm.com>
Cc: qemu-trivial@nongnu.org, raywang@linux.vnet.ibm.com,
qemu-devel@nongnu.org, afaerber@suse.de
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH 1/2] block:fix cloop.c coding style
Date: Wed, 02 Nov 2011 14:46:09 +0100 [thread overview]
Message-ID: <4EB149A1.9020507@redhat.com> (raw)
In-Reply-To: <1320222981-3839-1-git-send-email-wdongxu@linux.vnet.ibm.com>
Am 02.11.2011 09:36, schrieb Dong Xu Wang:
> From: Dong Xu Wang <wdongxu@linux.vnet.ibm.com>
>
> Fix coding style in block/cloop.c.
>
> v3: Split to 2 patches: one for fixing coding style, one for replacing free with
> g_free. And correct other 2 places with coding style problem.
> v2: Fix spelling: gfree->g_free.
> v1: Use gfree, to pair with g_malloc. Also fix coding style.
>
> Reviewed-by: Andreas Färber <afaerber@suse.de>
> Reviewed_by: Ray Wang <raywang@linux.vnet.ibm.com>
> Signed-off-by: Dong Xu Wang <wdongxu@linux.vnet.ibm.com>
Thanks, applied both to the block branch.
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Wolf <kwolf@redhat.com>
To: Dong Xu Wang <wdongxu@linux.vnet.ibm.com>
Cc: qemu-trivial@nongnu.org, raywang@linux.vnet.ibm.com,
qemu-devel@nongnu.org, afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH 1/2] block:fix cloop.c coding style
Date: Wed, 02 Nov 2011 14:46:09 +0100 [thread overview]
Message-ID: <4EB149A1.9020507@redhat.com> (raw)
In-Reply-To: <1320222981-3839-1-git-send-email-wdongxu@linux.vnet.ibm.com>
Am 02.11.2011 09:36, schrieb Dong Xu Wang:
> From: Dong Xu Wang <wdongxu@linux.vnet.ibm.com>
>
> Fix coding style in block/cloop.c.
>
> v3: Split to 2 patches: one for fixing coding style, one for replacing free with
> g_free. And correct other 2 places with coding style problem.
> v2: Fix spelling: gfree->g_free.
> v1: Use gfree, to pair with g_malloc. Also fix coding style.
>
> Reviewed-by: Andreas Färber <afaerber@suse.de>
> Reviewed_by: Ray Wang <raywang@linux.vnet.ibm.com>
> Signed-off-by: Dong Xu Wang <wdongxu@linux.vnet.ibm.com>
Thanks, applied both to the block branch.
Kevin
next prev parent reply other threads:[~2011-11-02 13:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-02 8:36 [Qemu-trivial] [PATCH 1/2] block:fix cloop.c coding style Dong Xu Wang
2011-11-02 8:36 ` [Qemu-devel] " Dong Xu Wang
2011-11-02 8:36 ` [Qemu-trivial] [PATCH 2/2] block:use g_free instead of free in cloop.c Dong Xu Wang
2011-11-02 8:36 ` [Qemu-devel] " Dong Xu Wang
2011-11-02 13:46 ` Kevin Wolf [this message]
2011-11-02 13:46 ` [Qemu-devel] [PATCH 1/2] block:fix cloop.c coding style Kevin Wolf
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=4EB149A1.9020507@redhat.com \
--to=kwolf@redhat.com \
--cc=afaerber@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=raywang@linux.vnet.ibm.com \
--cc=wdongxu@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 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.