From: patchwork-bot+netdevbpf@kernel.org
To: Gustavo A. R. Silva <gustavoars@kernel.org>
Cc: radhey.shyam.pandey@xilinx.com, davem@davemloft.net,
kuba@kernel.org, michal.simek@xilinx.com, netdev@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH][next] net: axienet: Fix fall-through warning for Clang
Date: Sun, 30 May 2021 20:50:02 +0000 [thread overview]
Message-ID: <162240780285.12384.17280549607346010508.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210528195831.GA39131@embeddedor>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Fri, 28 May 2021 14:58:31 -0500 you wrote:
> In preparation to enable -Wimplicit-fallthrough for Clang, fix multiple
> warnings by explicitly adding a fallthrough statement instead of just
> letting the code fall through to the next case.
>
> Link: https://github.com/KSPP/linux/issues/115
> Signed-off-by: Gustavo A. R. Silva <gustavoars@kernel.org>
>
> [...]
Here is the summary with links:
- [next] net: axienet: Fix fall-through warning for Clang
https://git.kernel.org/netdev/net-next/c/03a6ef31f2bc
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-05-30 20:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-28 19:58 [PATCH][next] net: axienet: Fix fall-through warning for Clang Gustavo A. R. Silva
2021-05-28 19:58 ` Gustavo A. R. Silva
2021-05-30 20:50 ` patchwork-bot+netdevbpf [this message]
2021-06-01 19:19 ` Kees Cook
2021-06-01 19:19 ` Kees Cook
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=162240780285.12384.17280549607346010508.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=gustavoars@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=netdev@vger.kernel.org \
--cc=radhey.shyam.pandey@xilinx.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 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.