All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Williams <patrick@stwcx.xyz>
To: OpenBMC List <openbmc@lists.ozlabs.org>
Subject: clang-15 in CI
Date: Fri, 30 Sep 2022 06:25:03 -0500	[thread overview]
Message-ID: <YzbSDyBFwmRc6TxM@heinlein> (raw)

[-- Attachment #1: Type: text/plain, Size: 1317 bytes --]

Hello,

TL;DR: I am updating clang and you might encounter minor CI issues as a result.
Generally these require re-running clang-format.

--

I'm going to merge a commit which updates our CI Docker image from
clang-14 to clang-15.  I've checked every repository that has a
.clang-tidy to ensure there are not any regressions and I've spot
checked a few repositories for clang-format issues.  I've seen one
clang-format incompatibility in sdbusplus (between 14 and 15) but
by tweaking some of the format flags I've been able to make it
consistent[1].

In clang-15, clang-format supports formatting of C++20 Concepts.  I've
proposed a set of small changes to our global .clang-format to utilize
this and a few other tweaks [2,3,4].

If you encounter any troubles with clang-format in the next few days you
probably just need to re-run it on the affected repository.  You might
consider copying over the latest global .clang-format as well.

The commit to update clang is [5].

1. https://gerrit.openbmc.org/c/openbmc/sdbusplus/+/57552
2. https://gerrit.openbmc.org/c/openbmc/docs/+/57556
3. https://gerrit.openbmc.org/c/openbmc/docs/+/57557
4. https://gerrit.openbmc.org/c/openbmc/docs/+/57558
5. https://gerrit.openbmc.org/c/openbmc/openbmc-build-scripts/+/57486

-- 
Patrick Williams

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

                 reply	other threads:[~2022-09-30 11:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YzbSDyBFwmRc6TxM@heinlein \
    --to=patrick@stwcx.xyz \
    --cc=openbmc@lists.ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.