Re: [PATCH v3 00/19] Update header guards bases on new coding style

[Frediano Ziglio <frediano.ziglio@xxxxxxxxx>]

On Thu, Oct 10, 2024 at 12:26 PM Andrew Cooper
<andrew.cooper3@xxxxxxxxxx> wrote:
>
> On 04/10/2024 9:16 am, Frediano Ziglio wrote:
> > Frediano Ziglio (19):
> >   xen: Update header guards - Generic
> >   xen: Update header guards - X86
> >   xen: Update header guards - ACPI
> >   xen: Update header guards - ARGO
> >   xen: Update header guards - ARM
> >   xen: Update header guards - Device tree
> >   xen: Update header guards - EFI
> >   xen: Update header guards - HYPFS
> >   xen: Update header guards - Intel TXT
> >   xen: Update header guards - I/O MMU
> >   xen: Update header guards - Kconfig
> >   xen: Update header guards - KEXEC
> >   xen: Update header guards - Live patch
> >   xen: Update header guards - PPC 64
> >   xen: Update header guards - RISC-V
> >   xen: Update header guards - Scheduling
> >   xen: Update header guards - VM event, mem access, monitor
> >   xen: Update header guards - VPCI
> >   xen: Update header guards - XSM/Flask
>
> This scheme is under dispute within the core maintainership.  One thing
> it has highlighted is that the MISRA identifier-length limit isn't being
> correctly enforced in Eclair right now.
>
> Please do not continue with this any further at this juncture.
>
> ~Andrew

No problems, I'll keep the branch and scripts waiting for correction
to our CODING_STYLE that are technically correct and agreed.
In the meantime, I would suggest to rollback the CODING_STYLE commit
about it, specifically commit a7201c021174efc908d939079db5bb2f89962a0d
"CODING_STYLE: header file guard naming rules".


Frediano