From: Joe Perches <joe@perches.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: clang-built-linux <clang-built-linux@googlegroups.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] .clang-format: Remove conditional comments
Date: Tue, 03 Nov 2020 16:56:06 -0800 [thread overview]
Message-ID: <f474396f8f47c303e3a3ac90a582c116e38e50e4.camel@perches.com> (raw)
In-Reply-To: <CANiq72=r6oieZ-Nj-e6e+HriW8kADB75z2pj6W-gg7Cff3nqGw@mail.gmail.com>
On Tue, 2020-11-03 at 22:33 +0100, Miguel Ojeda wrote:
> It is, yeah; however, the concern is that there may be developers
> running an old clang-format from their distro (i.e. not using it for
> compiling the kernel).
I expect that'd be extremely unusual.
> We need to compare the functionality advantage
> vs. the inconvenience of installing a current LLVM. The best would be
> to ask whoever is using it right now, but there is no easy way to do
> that -- many will only notice when the change is actually pushed :-)
Do remember that this patch is for the current kernel and
not any old version that someone might be compiling.
The current kernel _requires_ clang 10.0+ and that would
obviously provide clang-format 10+ as well.
next prev parent reply other threads:[~2020-11-04 0:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 18:29 Joe Perches
2020-11-03 21:33 ` Miguel Ojeda
2020-11-04 0:56 ` Joe Perches [this message]
2020-11-04 3:10 ` Miguel Ojeda
2020-11-04 3:15 ` Joe Perches
2020-11-04 3:57 ` Miguel Ojeda
2020-11-04 4:16 ` Joe Perches
2020-11-04 5:24 ` Miguel Ojeda
2020-11-04 1:08 ` Nick Desaulniers
2020-11-04 1:31 ` Joe Perches
2020-11-05 0:35 ` Nick Desaulniers
2020-11-05 6:44 ` Miguel Ojeda
2020-11-05 7:08 ` Joe Perches
2020-11-04 3:40 ` Miguel Ojeda
2020-11-05 0:33 ` Nick Desaulniers
2020-11-05 5:10 ` Miguel Ojeda
2020-11-04 1:11 ` Nick Desaulniers
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=f474396f8f47c303e3a3ac90a582c116e38e50e4.camel@perches.com \
--to=joe@perches.com \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®