From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Philip Li <philip.li@intel.com>, Nathan Chancellor <nathan@kernel.org>
Cc: Kees Cook <keescook@chromium.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
clang-built-linux <clang-built-linux@googlegroups.com>,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH] kbuild: Enable -Wimplicit-fallthrough for clang 14.0.0+
Date: Tue, 17 Aug 2021 23:45:48 -0500 [thread overview]
Message-ID: <d19dd1f7-3898-227a-3d7d-25cddb0434d0@embeddedor.com> (raw)
In-Reply-To: <20210818042720.GA1645557@pl-dbox>
On 8/17/21 23:27, Philip Li wrote:
>> Philip, how often is the kernel test robot's clang version rebuilt? Would it
>> be possible to bump it to latest ToT or at least
>> 9ed4a94d6451046a51ef393cd62f00710820a7e8 so that we do not get bit by this
>> warning when we go to enable this flag?
> Got it, currently we do upgrade in weekly cadence (but it may fall behind sometimes),
> and the one we use now is clang version 14.0.0 (https://github.com/llvm/llvm-project
> 2c6448cdc2f68f8c28fd0bd9404182b81306e6e6)
>
> We will ugrade to the head of llvm-project master today.
Thanks, Philip. We really appreciate it.
--
Gustavo
next prev parent reply other threads:[~2021-08-18 4:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210817005624.1455428-1-nathan@kernel.org>
[not found] ` <80fa539a-b767-76ed-dafa-4d8d1a6b063e@kernel.org>
[not found] ` <CAHk-=wgFXOf9OUh3+vmWjhp1PC47RVsUkL0NszBxSWhbGzx4tw@mail.gmail.com>
[not found] ` <5c856f36-69a7-e274-f72a-c3aef195adeb@kernel.org>
2021-08-17 18:03 ` [PATCH] kbuild: Enable -Wimplicit-fallthrough for clang 14.0.0+ Kees Cook
2021-08-17 18:25 ` Nathan Chancellor
2021-08-17 21:17 ` Masahiro Yamada
2021-08-17 21:33 ` Gustavo A. R. Silva
2021-08-17 23:06 ` Kees Cook
2021-08-17 23:23 ` Nathan Chancellor
2021-08-17 23:40 ` Gustavo A. R. Silva
2021-08-18 4:15 ` Masahiro Yamada
2021-08-18 4:27 ` Philip Li
2021-08-18 4:45 ` Gustavo A. R. Silva [this message]
2021-08-18 7:31 ` Philip Li
2021-08-18 12:12 ` Mark Brown
2021-08-25 21:09 ` 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=d19dd1f7-3898-227a-3d7d-25cddb0434d0@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=clang-built-linux@googlegroups.com \
--cc=gustavoars@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=philip.li@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox