All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ian Rogers <irogers@google.com>,
	Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] clang-format for v5.7-rc3
Date: Mon, 20 Apr 2020 21:09:16 +0200	[thread overview]
Message-ID: <20200420190916.GA11695@gmail.com> (raw)

Hi Linus,

The usual update for clang-format plus a requested C++ formatting change
(to align it with one of the C++ files we have).

Cheers,
Miguel

The following changes since commit 8f3d9f354286745c751374f5f1fcafee6b3f3136:

  Linux 5.7-rc1 (2020-04-12 12:35:55 -0700)

are available in the Git repository at:

  https://github.com/ojeda/linux.git tags/clang-format-for-linus-v5.7-rc3

for you to fetch changes up to 5d65a0218fee471e2cd512a8139ec857183b4721:

  clang-format: Update with the latest for_each macro list (2020-04-18 13:49:33 +0200)

----------------------------------------------------------------
Two trivial clang-format changes:

 - Don't indent C++ namespaces (Ian Rogers)

 - The usual clang-format macro list update (Miguel Ojeda)

----------------------------------------------------------------
Ian Rogers (1):
      clang-format: don't indent namespaces

Miguel Ojeda (1):
      clang-format: Update with the latest for_each macro list

 .clang-format | 18 ++++++++++++++----
 1 file changed, 14 insertions(+), 4 deletions(-)

             reply	other threads:[~2020-04-20 19:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-20 19:09 Miguel Ojeda [this message]
2020-04-21 19:09 ` [GIT PULL] clang-format for v5.7-rc3 Linus Torvalds
2020-04-21 21:03   ` Ian Rogers
2020-04-21 21:16     ` Linus Torvalds
2020-04-21 22:52       ` Miguel Ojeda
2020-04-21 19:40 ` 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=20200420190916.GA11695@gmail.com \
    --to=miguel.ojeda.sandonis@gmail.com \
    --cc=irogers@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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.