Standardizing Clang-Tidy Configuration Across OpenBMC Repositories

[Patrick Williams]

Some of this clang-tidy enablement didn't get fully rolled out to the
organization. One of the impediments was that it was difficult to agree
on clang-tidy settings and difficult to roll them out to the various
repositories.

I've written a tool named `config-clang-tidy` which can be used to
automate the roll-out of clang-tidy changes:
    https://gerrit.openbmc.org/c/openbmc/openbmc-build-scripts/+/80527

I used this tool to reformat the existing clang-tidy in entity-manager:
    https://gerrit.openbmc.org/c/openbmc/entity-manager/+/80530

Similarly, I used it against phosphor-virtual-sensor, which had a pretty
simple clang-tidy config, to both reformat and sync with docs:
    https://gerrit.openbmc.org/c/openbmc/phosphor-virtual-sensor/+/80531
    https://gerrit.openbmc.org/c/openbmc/phosphor-virtual-sensor/+/80532
-- 
Patrick Williams
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20250523/70f7ea22/attachment.sig>