From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: qemu-devel@nongnu.org
Cc: "Alexey Kardashevskiy" <aik@ozlabs.ru>,
"Alexander Graf" <agraf@suse.de>,
qemu-ppc@nongnu.org, "Paul Mackerras" <paulus@samba.org>,
"Andreas Färber" <afaerber@suse.de>,
"David Gibson" <david@gibson.dropbear.id.au>
Subject: [Qemu-devel] [PATCH v4 04/12] xics: replace fprintf with error_report
Date: Fri, 30 Aug 2013 15:28:25 +1000 [thread overview]
Message-ID: <1377840513-24882-5-git-send-email-aik@ozlabs.ru> (raw)
In-Reply-To: <1377840513-24882-1-git-send-email-aik@ozlabs.ru>
This replaces old-style fprintf with new style error_report.
Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
---
hw/intc/xics.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/hw/intc/xics.c b/hw/intc/xics.c
index 539a33a..cc4894d 100644
--- a/hw/intc/xics.c
+++ b/hw/intc/xics.c
@@ -29,6 +29,7 @@
#include "trace.h"
#include "hw/ppc/spapr.h"
#include "hw/ppc/xics.h"
+#include "qemu/error-report.h"
void xics_cpu_setup(XICSState *icp, PowerPCCPU *cpu)
{
@@ -48,8 +49,8 @@ void xics_cpu_setup(XICSState *icp, PowerPCCPU *cpu)
break;
default:
- fprintf(stderr, "XICS interrupt controller does not support this CPU "
- "bus model\n");
+ error_report("XICS interrupt controller does not support this CPU "
+ "bus model");
abort();
}
}
--
1.8.4.rc4
next prev parent reply other threads:[~2013-08-30 5:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-30 5:28 [Qemu-devel] [PATCH v4 00/12] xics: reworks and in-kernel support Alexey Kardashevskiy
2013-08-30 5:28 ` [Qemu-devel] [PATCH v4 01/12] target-ppc: Add helper for KVM_PPC_RTAS_DEFINE_TOKEN Alexey Kardashevskiy
2013-08-30 5:28 ` [Qemu-devel] [PATCH v4 02/12] xics: move reset and cpu_setup Alexey Kardashevskiy
2013-08-30 5:28 ` [Qemu-devel] [PATCH v4 03/12] spapr: move cpu_setup after kvmppc_set_papr Alexey Kardashevskiy
2013-08-30 5:28 ` Alexey Kardashevskiy [this message]
2013-09-23 14:58 ` [Qemu-devel] [PATCH v4 04/12] xics: replace fprintf with error_report Andreas Färber
2013-08-30 5:28 ` [Qemu-devel] [PATCH v4 05/12] xics: add pre_save/post_load dispatchers Alexey Kardashevskiy
2013-08-30 5:28 ` [Qemu-devel] [PATCH v4 06/12] xics: convert init() to realize() Alexey Kardashevskiy
2013-09-23 15:00 ` Andreas Färber
2013-08-30 5:28 ` [Qemu-devel] [PATCH v4 07/12] xics: add missing const specifiers to TypeInfo Alexey Kardashevskiy
2013-09-23 15:02 ` Andreas Färber
2013-08-30 5:28 ` [Qemu-devel] [PATCH v4 08/12] xics: split to xics and xics-common Alexey Kardashevskiy
2013-08-30 5:28 ` [Qemu-devel] [PATCH v4 09/12] xics: add cpu_setup callback Alexey Kardashevskiy
2013-08-30 5:28 ` [Qemu-devel] [PATCH v4 10/12] xics-kvm: Support for in-kernel XICS interrupt controller Alexey Kardashevskiy
2013-08-30 5:28 ` [Qemu-devel] [PATCH v4 11/12] xics: Implement H_IPOLL Alexey Kardashevskiy
2013-08-30 5:28 ` [Qemu-devel] [PATCH v4 12/12] xics: Implement H_XIRR_X Alexey Kardashevskiy
2013-09-04 2:56 ` [Qemu-devel] [PATCH v4 00/12] xics: reworks and in-kernel support Alexey Kardashevskiy
2013-09-10 4:26 ` Alexey Kardashevskiy
2013-09-16 4:10 ` Alexey Kardashevskiy
2013-09-23 2:01 ` Alexey Kardashevskiy
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=1377840513-24882-5-git-send-email-aik@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=david@gibson.dropbear.id.au \
--cc=paulus@samba.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).