From: Kevin Wolf <kwolf@redhat.com>
To: Charlie Shepherd <charlie@ctshepherd.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
gabriel@kerneis.info, qemu-devel@nongnu.org, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH] Test coroutine execution order (v2)
Date: Thu, 8 Aug 2013 12:16:07 +0200 [thread overview]
Message-ID: <20130808101607.GD7748@dhcp-200-207.str.redhat.com> (raw)
In-Reply-To: <5203695D.8040606@ctshepherd.com>
Am 08.08.2013 um 11:48 hat Charlie Shepherd geschrieben:
> Ah sorry I forgot it should go in the square brackets. Did you want
> me to resend it with the correct title?
Not necessary, I've fixed it up. Just remember it for your next series.
Thanks, applied to block-next (for 1.7)
Kevin
prev parent reply other threads:[~2013-08-08 10:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 19:11 [Qemu-devel] [PATCH] Test coroutine execution order Charlie Shepherd
2013-08-06 8:47 ` Kevin Wolf
2013-08-08 8:28 ` [Qemu-devel] [PATCH] Test coroutine execution order (v2) Stefan Hajnoczi
2013-08-08 9:48 ` Charlie Shepherd
2013-08-08 10:16 ` 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=20130808101607.GD7748@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).