Peter Maydell <[email protected]> writes:

> On 12 July 2016 at 15:31, Markus Armbruster <[email protected]> wrote:
>> The following changes since commit b35399bb4e9968296a12303b00f9f2066470e987:
>>
>>   Fix confusing argument names in some common functions (2016-07-12 13:06:08 
>> +0100)
>>
>> are available in the git repository at:
>>
>>   git://repo.or.cz/qemu/armbru.git tags/pull-include-2016-07-12
>>
>> for you to fetch changes up to 82751a32be872e71c22167234ac88ba52bf96a37:
>>
>>   cris: Fix broken header guard in hw/cris/boot.h (2016-07-12 16:20:46 +0200)
>>
>> ----------------------------------------------------------------
>> Clean up #include "..." vs <...> and header guards
>>
>> ----------------------------------------------------------------
>> 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
>
> Applied to master. Thanks for pushing this one through, this
> kind of big change can be a real pain to get into the tree...

It can be a real pain to rebase, so thank you for pulling it quickly :)

Reply via email to