diff options
| author | Markus Armbruster <armbru@redhat.com> | 2016-06-29 10:47:26 +0200 |
|---|---|---|
| committer | Markus Armbruster <armbru@redhat.com> | 2016-07-12 16:19:16 +0200 |
| commit | 3622634bc665244c2fd4382301cfadcef1a9e934 (patch) | |
| tree | e5aaf966e90d056d56601fea88a8494665f8999c /linux-user/ppc/target_cpu.h | |
| parent | 07f5a258750b3b9a6e10fd5ec3e29c9a943b650e (diff) | |
| download | qemu-3622634bc665244c2fd4382301cfadcef1a9e934.tar.gz qemu-3622634bc665244c2fd4382301cfadcef1a9e934.tar.bz2 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/ppc/target_cpu.h')
0 files changed, 0 insertions, 0 deletions