From: Kevin Wolf <kwolf@redhat.com>
To: Dong Xu Wang <wdongxu@linux.vnet.ibm.com>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH] block:add coroutine_fn marker to coroutine functions
Date: Thu, 10 Nov 2011 14:07:39 +0100 [thread overview]
Message-ID: <4EBBCC9B.7040302@redhat.com> (raw)
In-Reply-To: <1320913402-8762-1-git-send-email-wdongxu@linux.vnet.ibm.com>
Am 10.11.2011 09:23, schrieb Dong Xu Wang:
> From: Dong Xu Wang <wdongxu@linux.vnet.ibm.com>
>
> Looks better when reviewing these source files.
>
> Signed-off-by: Dong Xu Wang <wdongxu@linux.vnet.ibm.com>
Thanks, applied to the block branch (for 1.1)
Kevin
prev parent reply other threads:[~2011-11-10 13:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-10 8:23 [Qemu-trivial] [PATCH] block:add coroutine_fn marker to coroutine functions Dong Xu Wang
2011-11-10 11:32 ` Stefan Hajnoczi
2011-11-10 13:28 ` [Qemu-trivial] [Qemu-devel] " Dong Xu Wang
2011-11-10 13:07 ` 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=4EBBCC9B.7040302@redhat.com \
--to=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--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 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).