linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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-rc1
Date: Tue, 9 Jul 2019 13:20:10 -0500	[thread overview]
Message-ID: <20190709182010.GA32200@embeddedor> (raw)

The following changes since commit cd6c84d8f0cdc911df435bb075ba22ce3c605b07:

  Linux 5.2-rc2 (2019-05-26 16:49:19 -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-rc1

for you to fetch changes up to d93512ef0f0efa17eded6b9edf8e88e8418f44bd:

  Makefile: Globally enable fall-through warning (2019-07-08 15:23:22 -0500)

----------------------------------------------------------------
Wimplicit-fallthrough patches for 5.3-rc1

Hi Linus,

Please, pull the following patches that mark switch cases where we are
expecting to fall through. These patches are part of the ongoing efforts
to enable -Wimplicit-fallthrough. All of them have been baking in linux-next
for a whole development cycle.

Also, pull the Makefile patch that universally enables the
-Wimplicit-fallthrough option.

Thanks

Signed-off-by: Gustavo A. R. Silva <gustavo@embeddedor.com>

----------------------------------------------------------------
Gustavo A. R. Silva (6):
      afs: fsclient: Mark expected switch fall-throughs
      afs: yfsclient: Mark expected switch fall-throughs
      can: mark expected switch fall-throughs
      firewire: mark expected switch fall-throughs
      platform/x86: acer-wmi: Mark expected switch fall-throughs
      Makefile: Globally enable fall-through warning

 Documentation/process/deprecated.rst          | 14 +++++++
 Makefile                                      |  3 ++
 drivers/firewire/core-device.c                |  2 +-
 drivers/firewire/core-iso.c                   |  2 +-
 drivers/firewire/core-topology.c              |  1 +
 drivers/net/can/at91_can.c                    |  6 ++-
 drivers/net/can/peak_canfd/peak_pciefd_main.c |  2 +-
 drivers/net/can/spi/mcp251x.c                 |  3 +-
 drivers/net/can/usb/peak_usb/pcan_usb.c       |  2 +-
 drivers/platform/x86/acer-wmi.c               |  4 ++
 fs/afs/fsclient.c                             | 51 ++++++++++++++++---------
 fs/afs/yfsclient.c                            | 54 +++++++++++++++++----------
 12 files changed, 100 insertions(+), 44 deletions(-)

             reply	other threads:[~2019-07-09 18:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-09 18:20 Gustavo A. R. Silva [this message]
2019-07-10  4:15 ` [GIT PULL] Wimplicit-fallthrough patches for 5.3-rc1 Stephen Rothwell
2019-07-10 18:14   ` Gustavo A. R. Silva
2019-07-10 21:36     ` Stephen Rothwell
2019-07-18 20:28       ` Gustavo A. R. Silva
2019-07-21 21:13         ` Gustavo A. R. Silva

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=20190709182010.GA32200@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).