This series takes a good swing at two annoyances:
* We sometimes use #include "..." even for system headers, and <...>
for our own headers. Makes spotting the system headers harder, and
can be confusing. PATCH 01 cleans this up. You've seen it before
as "[PATCH RFC v2 1/5] Use #include "..." exactly for our own
headers", but I've since replaced the bugs in my Perl script by less
stupid ones, which made the patch grow.
* Our use of header guards is rather sloppy. Sloppiness there can
lead to confusing compilation errors. The rest of the series cleans
up existing header guards. In particular, it normalizes guard
symbols to follow a common pattern, in the hope of making clashes
less likely. It doesn't add new header guards. We have almost 150
headers without a recognizable header guard. A few of them are for
multiple inclusion, a few more don't need header guards because they
don't do anything but include, but the majority probably should have
one. Left for another day.
Markus Armbruster (18):
Use #include "..." for our own headers, <...> for others
scripts: New clean-header-guards.pl
target-*: Clean up cpu.h header guards
linux-user: Clean up target_syscall.h header guards
linux-user: Clean up target_cpu.h header guards
linux-user: Clean up target_signal.h header guards
linux-user: Clean up target_structs.h header guards
linux-user: Clean up hostdep.h header guards
linux-user: Fix broken header guard in syscall_defs.h
tcg: Clean up tcg-target.h header guards
spapr_pci: Include spapr.h instead of playing games with #error
Drop Emacs local variables lists redundant with .dir-locals.el
Clean up header guards that don't match their file name
libdecnumber: Don't fool around with guards to avoid #include
libdecnumber: Don't error out on decNumberLocal.h re-inclusion
Clean up ill-advised or unusual header guards
Clean up decorations and whitespace around header guards
cris: Fix broken header guard in hw/cris/boot.h