From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Kees Cook <keescook@chromium.org>,
Greg KH <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>
Subject: [GIT PULL] Wimplicit-fallthrough patches for 5.3-rc5
Date: Wed, 14 Aug 2019 13:49:01 -0500 [thread overview]
Message-ID: <20190814184901.GA16709@embeddedor> (raw)
The following changes since commit 609488bc979f99f805f34e9a32c1e3b71179d10b:
Linux 5.3-rc2 (2019-07-28 12:47:02 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gustavoars/linux.git tags/Wimplicit-fallthrough-5.3-rc5
for you to fetch changes up to 1ee1119d184bb06af921b48c3021d921bbd85bac:
sh: kernel: hw_breakpoint: Fix missing break in switch statement (2019-08-11 16:15:16 -0500)
----------------------------------------------------------------
Wimplicit-fallthrough patches for 5.3-rc5
Hi Linus,
Please, pull the following patches that fix sh mainline builds:
- Fix fall-through warnings in sh.
- Fix missing break bug (a 10-year-old bug) in sh. This
fix is tagged for stable.
Currently, mainline builds for sh are broken. These patches fix that.
Thanks
Signed-off-by: Gustavo A. R. Silva <gustavo@embeddedor.com>
----------------------------------------------------------------
Gustavo A. R. Silva (2):
sh: kernel: disassemble: Mark expected switch fall-throughs
sh: kernel: hw_breakpoint: Fix missing break in switch statement
arch/sh/kernel/disassemble.c | 5 ++---
arch/sh/kernel/hw_breakpoint.c | 1 +
2 files changed, 3 insertions(+), 3 deletions(-)
next reply other threads:[~2019-08-14 18:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 18:49 Gustavo A. R. Silva [this message]
2019-08-14 22:35 ` [GIT PULL] Wimplicit-fallthrough patches for 5.3-rc5 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=20190814184901.GA16709@embeddedor \
--to=gustavo@embeddedor.com \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.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 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).