From: Gerd Hoffmann <kraxel@redhat.com>
To: Alon Levy <alevy@redhat.com>
Cc: airlied@redhat.com, Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] make screendump an async command
Date: Mon, 17 Jun 2013 16:00:50 +0200 [thread overview]
Message-ID: <51BF1692.7020100@redhat.com> (raw)
In-Reply-To: <1371461430.21763.5.camel@localhost>
On 06/17/13 11:30, Alon Levy wrote:
> But on the other hand if this is something that would be acceptable now
> and having proper Async error handling is not forthcoming (why btw? is
> anyone working on it) . But it would become baggage later on..
Don't think it is too bad, RfC patches will go out in a moment ...
cheers,
Gerd
next prev parent reply other threads:[~2013-06-17 14:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 19:27 [Qemu-devel] [PATCH] make screendump an async command Alon Levy
2013-06-13 20:08 ` Paolo Bonzini
2013-06-13 20:35 ` Alon Levy
2013-06-14 11:18 ` Gerd Hoffmann
2013-06-14 18:02 ` Alon Levy
2013-06-14 18:07 ` Alon Levy
2013-06-14 18:21 ` Anthony Liguori
2013-06-14 23:55 ` Alon Levy
2013-06-17 13:41 ` Luiz Capitulino
2013-06-17 6:06 ` Gerd Hoffmann
2013-06-17 9:30 ` Alon Levy
2013-06-17 14:00 ` Gerd Hoffmann [this message]
2013-06-17 13:54 ` Luiz Capitulino
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=51BF1692.7020100@redhat.com \
--to=kraxel@redhat.com \
--cc=airlied@redhat.com \
--cc=alevy@redhat.com \
--cc=aliguori@us.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).