From: Paolo Bonzini <pbonzini@redhat.com>
To: "Cao,Bing Bu" <mars@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] creen dump not supported when no console
Date: Sun, 20 Nov 2011 12:02:44 +0100 [thread overview]
Message-ID: <4EC8DE54.20802@redhat.com> (raw)
In-Reply-To: <1321781468-11126-1-git-send-email-mars@linux.vnet.ibm.com>
On 11/20/2011 10:31 AM, Cao,Bing Bu wrote:
> + } else {
> + fprintf(stderr,"no any console,could not screen dump \n");
> + return;
This should be error_printf.
Paolo
next prev parent reply other threads:[~2011-11-20 11:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-18 15:47 [Qemu-devel] [PATCH] console: Fix segfault on screendump without VGA adapter Alexander Graf
2011-11-20 9:31 ` [Qemu-devel] [PATCH] creen dump not supported when no console Cao,Bing Bu
2011-11-20 11:02 ` Paolo Bonzini [this message]
2011-11-22 1:26 ` [Qemu-devel] [PATCH][V2] Can't screendump without a console Cao,Bing Bu
2011-11-21 12:30 ` [Qemu-devel] [PATCH] creen dump not supported when no console Markus Armbruster
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=4EC8DE54.20802@redhat.com \
--to=pbonzini@redhat.com \
--cc=mars@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).