linux-user: Clean up target_syscall.h header guards
commit3622634bc665244c2fd4382301cfadcef1a9e934
authorMarkus Armbruster <armbru@redhat.com>
Wed, 29 Jun 2016 08:47:26 +0000 (29 10:47 +0200)
committerMarkus Armbruster <armbru@redhat.com>
Tue, 12 Jul 2016 14:19:16 +0000 (12 16:19 +0200)
treee5aaf966e90d056d56601fea88a8494665f8999c
parent07f5a258750b3b9a6e10fd5ec3e29c9a943b650e
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>
18 files changed:
linux-user/aarch64/target_syscall.h
linux-user/alpha/target_syscall.h
linux-user/arm/target_syscall.h
linux-user/cris/target_syscall.h
linux-user/i386/target_syscall.h
linux-user/m68k/target_syscall.h
linux-user/microblaze/target_syscall.h
linux-user/mips/target_syscall.h
linux-user/mips64/target_syscall.h
linux-user/openrisc/target_syscall.h
linux-user/ppc/target_syscall.h
linux-user/s390x/target_syscall.h
linux-user/sh4/target_syscall.h
linux-user/sparc/target_syscall.h
linux-user/sparc64/target_syscall.h
linux-user/tilegx/target_syscall.h
linux-user/unicore32/target_syscall.h
linux-user/x86_64/target_syscall.h