From: Kevin Wolf <kwolf@redhat.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH -V2] coroutine: Add CoRwlock support
Date: Fri, 29 Jul 2011 17:32:07 +0200 [thread overview]
Message-ID: <4E32D277.1020901@redhat.com> (raw)
In-Reply-To: <87fwlp17x1.fsf@skywalker.in.ibm.com>
Am 29.07.2011 16:24, schrieb Aneesh Kumar K.V:
> On Fri, 29 Jul 2011 14:53:14 +0200, Kevin Wolf <kwolf@redhat.com> wrote:
>> Am 27.07.2011 18:21, schrieb Aneesh Kumar K.V:
>>> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
>>> ---
>>> qemu-coroutine-lock.c | 44 ++++++++++++++++++++++++++++++++++++++++++++
>>> qemu-coroutine.h | 12 ++++++++++++
>>> 2 files changed, 56 insertions(+), 0 deletions(-)
>>
>> Looks good to me.
>>
>> What's your plan with getting this merged? Are you going to just include
>> it with another series that you'll send once the basic coroutine support
>> is in?
>
> Since the patch already is dependent on CoQueue, it would be nice if you
> can push it through your tree. I will stage the dependent VirtFS patch
> after that get merged upstream.
Okay, I applied it to my branch so that I won't forget about it, but
while merging I noticed two things that you could fix: The patch adds an
#include "qemu-thread.h" to qemu-coroutine.h for apparently no reason,
and it would be nice to have comments in qemu-coroutine.h like all other
functions have.
Kevin
prev parent reply other threads:[~2011-07-29 15:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 16:21 [Qemu-devel] [PATCH -V2] coroutine: Add CoRwlock support Aneesh Kumar K.V
2011-07-29 12:53 ` Kevin Wolf
2011-07-29 14:24 ` Aneesh Kumar K.V
2011-07-29 15:32 ` 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=4E32D277.1020901@redhat.com \
--to=kwolf@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=aneesh.kumar@linux.vnet.ibm.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).