From: Kevin Wolf <kwolf@redhat.com>
To: Gabriel Kerneis <gabriel@kerneis.info>
Cc: Charlie Shepherd <charlie@ctshepherd.com>,
pbonzini@redhat.com, qemu-devel@nongnu.org, stefanha@gmail.com
Subject: Re: [Qemu-devel] [RFC] Introducing CoroCheck and proposal for a blocking_fn annotation
Date: Fri, 6 Sep 2013 18:28:10 +0200 [thread overview]
Message-ID: <20130906162810.GO2588@dhcp-200-207.str.redhat.com> (raw)
In-Reply-To: <20130906160519.GA7913@kerneis.info>
Am 06.09.2013 um 18:05 hat Gabriel Kerneis geschrieben:
> On Fri, Sep 06, 2013 at 04:36:47PM +0100, Charlie Shepherd wrote:
> > However, I'm not sure it makes sense to use blocking_fn until the
> > convert-block series (which currently needs a respin after Stefan's
> > review) is fully upstreamed. Maybe this patch makes most sense at
> > the start of that series?
>
> Yes, definitely, that's why I labeled it RFC rather than PATCH. But if
> people agree, it would make much more sense to have the annotations
> within your patch series rather than added later (notwithstanding the
> fact that it would ease your refactoring effort).
Makes sense to me, go ahead and put it to use.
Kevin
prev parent reply other threads:[~2013-09-06 16:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-06 14:30 [Qemu-devel] [RFC] Introducing CoroCheck and proposal for a blocking_fn annotation Gabriel Kerneis
2013-09-06 14:30 ` [Qemu-devel] [RFC] Introduce " Gabriel Kerneis
2013-09-06 14:46 ` [Qemu-devel] [RFC] Introducing CoroCheck and proposal for a " Gabriel Kerneis
2013-09-06 15:36 ` Charlie Shepherd
2013-09-06 16:05 ` Gabriel Kerneis
2013-09-06 16:28 ` 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=20130906162810.GO2588@dhcp-200-207.str.redhat.com \
--to=kwolf@redhat.com \
--cc=charlie@ctshepherd.com \
--cc=gabriel@kerneis.info \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).