summaryrefslogtreecommitdiffstats
path: root/linux-user/i386
diff options
context:
space:
mode:
authorMarkus Armbruster2016-06-29 10:47:26 +0200
committerMarkus Armbruster2016-07-12 16:19:16 +0200
commit3622634bc665244c2fd4382301cfadcef1a9e934 (patch)
treee5aaf966e90d056d56601fea88a8494665f8999c /linux-user/i386
parenttarget-*: Clean up cpu.h header guards (diff)
downloadqemu-3622634bc665244c2fd4382301cfadcef1a9e934.tar.gz
qemu-3622634bc665244c2fd4382301cfadcef1a9e934.tar.xz
qemu-3622634bc665244c2fd4382301cfadcef1a9e934.zip
linux-user: Clean up target_syscall.h header guards
Some of them use guard symbol TARGET_SYSCALL_H, but we also have CRIS_SYSCALL_H, MICROBLAZE_SYSCALLS_H, TILEGX_SYSCALLS_H and __UC32_SYSCALL_H__. They all upset scripts/clean-header-guards.pl. Reuse of the same guard symbol TARGET_SYSCALL_H in multiple headers is okay as long as they cannot be included together. The script can't tell, so it warns. The script dislikes the other guard symbols, too. They don't match their file name (they should, to make guard collisions less likely), and __UC32_SYSCALL_H__ is a reserved identifier. Clean them all up: use guard symbol $target_TARGET_SYSCALL_H for linux-user/$target/target_sycall.h. Signed-off-by: Markus Armbruster <armbru@redhat.com> Reviewed-by: Richard Henderson <rth@twiddle.net>
Diffstat (limited to 'linux-user/i386')
-rw-r--r--linux-user/i386/target_syscall.h6
1 files changed, 3 insertions, 3 deletions
diff --git a/linux-user/i386/target_syscall.h b/linux-user/i386/target_syscall.h
index 0ac84dc02f..b4e895fd9c 100644
--- a/linux-user/i386/target_syscall.h
+++ b/linux-user/i386/target_syscall.h
@@ -1,5 +1,5 @@
-#ifndef TARGET_SYSCALL_H
-#define TARGET_SYSCALL_H
+#ifndef I386_TARGET_SYSCALL_H
+#define I386_TARGET_SYSCALL_H
/* default linux values for the selectors */
#define __USER_CS (0x23)
@@ -154,4 +154,4 @@ struct target_vm86plus_struct {
#define TARGET_MLOCKALL_MCL_CURRENT 1
#define TARGET_MLOCKALL_MCL_FUTURE 2
-#endif /* TARGET_SYSCALL_H */
+#endif /* I386_TARGET_SYSCALL_H */