From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: David Gibson <dgibson@redhat.com>, qemu-ppc@nongnu.org
Subject: [Qemu-devel] [PATCH] ppc: avoid typedef redefinitions
Date: Fri, 3 Mar 2017 17:28:50 +0100 [thread overview]
Message-ID: <1488558530-21016-3-git-send-email-pbonzini@redhat.com> (raw)
These cause compilation failures on CentOS 6 or other operating
systems with older GCCs.
Cc: David Gibson <dgibson@redhat.com>
Cc: qemu-ppc@nongnu.org
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
---
It would probably be better to remove the
sPAPRMachineState typedef from xics.h instead,
but this is a quick fix to restore the centos6
docker target.
include/hw/ppc/spapr.h | 1 -
include/hw/ppc/xics.h | 4 ++--
2 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/include/hw/ppc/spapr.h b/include/hw/ppc/spapr.h
index cfd2711..15f4371 100644
--- a/include/hw/ppc/spapr.h
+++ b/include/hw/ppc/spapr.h
@@ -21,7 +21,6 @@ typedef struct sPAPREventSource sPAPREventSource;
#define SPAPR_TIMEBASE_FREQ 512000000ULL
typedef struct sPAPRMachineClass sPAPRMachineClass;
-typedef struct sPAPRMachineState sPAPRMachineState;
#define TYPE_SPAPR_MACHINE "spapr-machine"
#define SPAPR_MACHINE(obj) \
diff --git a/include/hw/ppc/xics.h b/include/hw/ppc/xics.h
index 1945913..9a5e715 100644
--- a/include/hw/ppc/xics.h
+++ b/include/hw/ppc/xics.h
@@ -139,9 +139,9 @@ struct ICSIRQState {
uint8_t flags;
};
-typedef struct XICSFabric {
+struct XICSFabric {
Object parent;
-} XICSFabric;
+};
#define TYPE_XICS_FABRIC "xics-fabric"
#define XICS_FABRIC(obj) \
--
1.8.3.1
next reply other threads:[~2017-03-03 16:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 16:28 Paolo Bonzini [this message]
2017-03-04 16:30 ` [Qemu-devel] [PATCH] ppc: avoid typedef redefinitions Peter Maydell
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=1488558530-21016-3-git-send-email-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=dgibson@redhat.com \
--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).