From: Miguel Ojeda <ojeda@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Mickaël Salaün" <mic@digikod.net>,
"Brian Norris" <briannorris@chromium.org>,
"Tom Rix" <trix@redhat.com>, "Miguel Ojeda" <ojeda@kernel.org>,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] clang-format for v5.19-rc1
Date: Fri, 27 May 2022 19:22:24 +0200 [thread overview]
Message-ID: <20220527172209.GA15519@kernel.org> (raw)
Hi Linus,
Please pull these changes to clang-format. Thanks!
Cheers,
Miguel
The following changes since commit 42226c989789d8da4af1de0c31070c96726d990c:
Linux 5.18-rc7 (2022-05-15 18:08:58 -0700)
are available in the Git repository at:
https://github.com/ojeda/linux.git tags/clang-format-for-linus-v5.19-rc1
for you to fetch changes up to 781121a7f6d11d7cae44982f174ea82adeec7db0:
clang-format: Fix space after for_each macros (2022-05-20 19:27:16 +0200)
----------------------------------------------------------------
clang-format modernization and cleanups
A few changes from Brian Norris and Mickaël Salaün to start taking
advantage of some clang-format 11 features, plus a few cleanups
and the usual update of the macro list.
----------------------------------------------------------------
Brian Norris (1):
clang-format: Fix space after for_each macros
Mickaël Salaün (3):
clang-format: Extend the for_each list with tools/
clang-format: Update to clang-format >= 6
clang-format: Fix goto labels indentation
Miguel Ojeda (3):
clang-format: Update with v5.18-rc7's `for_each` macro list
clang-format: Use POSIX locale for `sort`
clang-format: Simplify command with `sort -u`
.clang-format | 218 +++++++++++++++++++++++++++++++++++++++++++++-------------
1 file changed, 170 insertions(+), 48 deletions(-)
next reply other threads:[~2022-05-27 17:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 17:22 Miguel Ojeda [this message]
2022-05-28 1:21 ` [GIT PULL] clang-format for v5.19-rc1 pr-tracker-bot
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=20220527172209.GA15519@kernel.org \
--to=ojeda@kernel.org \
--cc=briannorris@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mic@digikod.net \
--cc=torvalds@linux-foundation.org \
--cc=trix@redhat.com \
/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.