linux-kernel - Re: [GIT PULL] clang-format for v5.7-rc3

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CANiq72n2T0UCdjb923LThts-3js8LiDTqFHB-PK3SqeG3xwY=w@mail.gmail.com>
Date:   Wed, 22 Apr 2020 00:52:14 +0200
From:   Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Ian Rogers <irogers@...gle.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] clang-format for v5.7-rc3

On Tue, Apr 21, 2020 at 11:17 PM Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> Well, not really. I _did_ check the commit message. It says nothing
> very useful at all, in that the kernel doesn't use C++ (aside from a
> couple of clang tests)

Apart from what Ian said, one of those is tools/perf/util/c++/clang.{h,cpp}
which use `namespace perf` (with non-indented contents), which is why
I mentioned in the PR email that the change aligns clang-format to the
current usage.

But yeah, perhaps I should have edited the commit message rather than
say it in the email in passing.

Cheers,
Miguel