From: "Gustavo A. R. Silva" <gustavoars@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Kees Cook <keescook@chromium.org>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org,
"Gustavo A. R. Silva" <gustavoars@kernel.org>
Subject: [GIT PULL] Enable -Wimplicit-fallthrough for Clang for 5.15-rc2
Date: Tue, 14 Sep 2021 11:41:00 -0500 [thread overview]
Message-ID: <20210914164100.GA236780@embeddedor> (raw)
The following changes since commit 6880fa6c56601bb8ed59df6c30fd390cc5f6dd8f:
Linux 5.15-rc1 (2021-09-12 16:28:37 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gustavoars/linux.git tags/implicit-fallthrough-clang-5.15-rc2
for you to fetch changes up to 236378bb6ca791cbde68eacedd7688084d06177e:
Makefile: Enable -Wimplicit-fallthrough for Clang (2021-09-13 23:47:12 -0500)
----------------------------------------------------------------
Enable -Wimplicit-fallthrough for Clang for 5.15-rc2
Hi Linus,
Please, pull the following patches that fix the last warnings in
x86_64, ARM and MIPS reported by kernel test robot, and enables
-Wimplicit-fallthrough for Clang 14+, globally.
We had almost 40,000[1] of these issues for Clang in the beginning,
and there might be a couple more out there when building some
architectures with certain configurations. However, with the
recent fixes, I think we are in good shape and it is now possible
to enable -Wimplicit-fallthrough for Clang, with this finally getting rid of
the unintentional fallthrough bug-class in the kernel, entirely. :)
[1] https://github.com/KSPP/linux/issues/115
Thanks!
----------------------------------------------------------------
Gustavo A. R. Silva (4):
scsi: st: Fix fall-through warning for Clang
MIPS: Fix fall-through warnings for Clang
pcmcia: db1xxx_ss: Fix fall-through warning for Clang
Makefile: Enable -Wimplicit-fallthrough for Clang
Makefile | 8 ++++++++
arch/mips/alchemy/devboards/db1550.c | 1 +
arch/mips/kernel/uprobes.c | 1 +
drivers/pcmcia/db1xxx_ss.c | 1 +
drivers/scsi/st.c | 1 +
5 files changed, 12 insertions(+)
reply other threads:[~2021-09-14 16:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210914164100.GA236780@embeddedor \
--to=gustavoars@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.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;
as well as URLs for NNTP newsgroup(s).