Ethernet Bridge development
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: "Gustavo A. R. Silva" <gustavoars@kernel.org>
Cc: netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org, nikolay@nvidia.com,
	roopa@nvidia.com, kuba@kernel.org, davem@davemloft.net,
	linux-hardening@vger.kernel.org
Subject: Re: [Bridge] [PATCH RESEND][next] net: bridge: Fix fall-through warnings for Clang
Date: Wed, 10 Mar 2021 21:00:12 +0000	[thread overview]
Message-ID: <161541001297.4631.3343209004781162292.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210310054115.GA285785@embeddedor>

Hello:

This patch was applied to netdev/net-next.git (refs/heads/master):

On Tue, 9 Mar 2021 23:41:15 -0600 you wrote:
> In preparation to enable -Wimplicit-fallthrough for Clang, fix a warning
> by explicitly adding a break statement instead of letting the code fall
> through to the next case.
> 
> Link: https://github.com/KSPP/linux/issues/115
> Acked-by: Nikolay Aleksandrov <nikolay@nvidia.com>
> Signed-off-by: Gustavo A. R. Silva <gustavoars@kernel.org>
> 
> [...]

Here is the summary with links:
  - [RESEND,next] net: bridge: Fix fall-through warnings for Clang
    https://git.kernel.org/netdev/net-next/c/ecd1c6a51fcc

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2021-03-10 21:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-10  5:41 [Bridge] [PATCH RESEND][next] net: bridge: Fix fall-through warnings for Clang Gustavo A. R. Silva
2021-03-10 21:00 ` patchwork-bot+netdevbpf [this message]

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=161541001297.4631.3343209004781162292.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=bridge@lists.linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=gustavoars@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nikolay@nvidia.com \
    --cc=roopa@nvidia.com \
    /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