From: Glauber Costa <glommer@redhat.com>
To: qemu-devel@nongnu.org
Cc: jan.kiszka@siemens.com, aliguori@us.ibm.com, jes@sgi.com,
avi@qumranet.com, dmitry.baryshkov@siemens.com
Subject: [Qemu-devel] [PATCH 1/7] protect accel.h from multiple inclusion
Date: Mon, 13 Oct 2008 22:51:42 -0200 [thread overview]
Message-ID: <1223945508-22241-2-git-send-email-glommer@redhat.com> (raw)
In-Reply-To: <1223945508-22241-1-git-send-email-glommer@redhat.com>
Allow it to be included multiple times.
Signed-off-by: Glauber Costa <glommer@redhat.com>
---
accel.h | 5 ++++-
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/accel.h b/accel.h
index ae72e23..f41ec72 100644
--- a/accel.h
+++ b/accel.h
@@ -1,3 +1,6 @@
+#ifndef _ACCEL_H_
+#define _ACCEL_H_
+
typedef struct QEMUAccel {
char *name;
void (*cpu_interrupt)(CPUState *env);
@@ -144,4 +147,4 @@ static inline int accel_break_loop(CPUState *env)
}
extern void accel_add(const char *name);
-
+#endif
--
1.5.5.1
next prev parent reply other threads:[~2008-10-13 22:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 0:51 [Qemu-devel] [PATCH 0/7] Update qemu accel Glauber Costa
2008-10-14 0:51 ` Glauber Costa [this message]
2008-10-14 0:51 ` [Qemu-devel] [PATCH 2/7] use accel_trace_io in calling sites Glauber Costa
2008-10-14 0:51 ` [Qemu-devel] [PATCH 3/7] use break_loop accel Glauber Costa
2008-10-14 0:51 ` [Qemu-devel] [PATCH 4/7] give noaccel a name Glauber Costa
2008-10-14 16:00 ` [Qemu-devel] " Avi Kivity
2008-10-14 16:04 ` Glauber Costa
2008-10-14 0:51 ` [Qemu-devel] [PATCH 5/7] check wether kqemu is enabled in open code Glauber Costa
2008-10-14 0:51 ` [Qemu-devel] [PATCH 6/7] provide an opaque for accelerator in cpu state Glauber Costa
2008-10-14 0:51 ` [Qemu-devel] [PATCH 7/7] Revert "don't allocate ram before accel starts" Glauber Costa
2008-10-14 16:02 ` [Qemu-devel] Re: [PATCH 0/7] Update qemu accel Anthony Liguori
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=1223945508-22241-2-git-send-email-glommer@redhat.com \
--to=glommer@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=avi@qumranet.com \
--cc=dmitry.baryshkov@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=jes@sgi.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).