From: Glauber Costa <glommer@gmail.com>
To: Glauber Costa <glommer@redhat.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/2] IO-thread fixes again
Date: Wed, 7 Oct 2009 16:36:59 -0300 [thread overview]
Message-ID: <5d6222a80910071236o5d67a269x9e00be26eec867ab@mail.gmail.com> (raw)
In-Reply-To: <1254941388-12556-1-git-send-email-glommer@redhat.com>
And I forgot to fix the SoB AGAIN!
sorry dudes
On Wed, Oct 7, 2009 at 3:49 PM, Glauber Costa <glommer@redhat.com> wrote:
> Since the last one broke the build for !IO_THREAD, here it goes
> a version that (at least in my boxes) does not.
>
>
>
>
--
Glauber Costa.
"Free as in Freedom"
http://glommer.net
"The less confident you are, the more serious you have to act."
prev parent reply other threads:[~2009-10-07 19:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-07 18:49 [Qemu-devel] [PATCH 0/2] IO-thread fixes again Glauber Costa
2009-10-07 18:49 ` [Qemu-devel] [PATCH 1/2] unlock iothread mutex before running kvm ioctl Glauber Costa
2009-10-07 18:49 ` [Qemu-devel] [PATCH 2/2] do proper cpu_self check Glauber Costa
2009-10-07 19:36 ` Glauber Costa [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=5d6222a80910071236o5d67a269x9e00be26eec867ab@mail.gmail.com \
--to=glommer@gmail.com \
--cc=aliguori@us.ibm.com \
--cc=glommer@redhat.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).