From: "Gustavo A. R. Silva" <gustavoars@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Kees Cook <keescook@chromium.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org,
"Gustavo A. R. Silva" <gustavoars@kernel.org>
Subject: [GIT PULL] fallthrough fixes for Clang for 5.16-rc1
Date: Mon, 1 Nov 2021 17:01:20 -0500 [thread overview]
Message-ID: <20211101220120.GA30083@embeddedor> (raw)
The following changes since commit e4e737bb5c170df6135a127739a9e6148ee3da82:
Linux 5.15-rc2 (2021-09-19 17:28:22 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gustavoars/linux.git tags/fallthrough-fixes-clang-5.16-rc1
for you to fetch changes up to 02900f428d3c7acd89b77784bec33ddec7b750a4:
pcmcia: db1xxx_ss: Fix fall-through warning for Clang (2021-10-13 14:47:48 -0500)
----------------------------------------------------------------
fallthrough fixes for Clang for 5.16-rc1
Hi Linus,
Please, pull the following patches that fix some fall-through warnings
when building with Clang and -Wimplicit-fallthrough.
Thanks!
--
Gustavo
----------------------------------------------------------------
Gustavo A. R. Silva (3):
scsi: st: Fix fall-through warning for Clang
MIPS: Fix fall-through warnings for Clang
pcmcia: db1xxx_ss: Fix fall-through warning for Clang
arch/mips/alchemy/devboards/db1550.c | 1 +
arch/mips/kernel/uprobes.c | 1 +
drivers/pcmcia/db1xxx_ss.c | 1 +
drivers/scsi/st.c | 1 +
4 files changed, 4 insertions(+)
next reply other threads:[~2021-11-01 21:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 22:01 Gustavo A. R. Silva [this message]
2021-11-02 0:51 ` [GIT PULL] fallthrough fixes for Clang for 5.16-rc1 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=20211101220120.GA30083@embeddedor \
--to=gustavoars@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--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.