From: patchwork-bot+netdevbpf@kernel•org
To: Maciej Fijalkowski <maciej.fijalkowski@intel•com>
Cc: bpf@vger•kernel.org, ast@kernel•org, daniel@iogearbox•net,
sfr@canb•auug.org.au, andrii@kernel•org, netdev@vger•kernel.org,
magnus.karlsson@intel•com, linux-next@vger•kernel.org
Subject: Re: [PATCH bpf-next 0/2] xsk: remove reduntant 'falltrough' attributes
Date: Thu, 21 Apr 2022 14:40:12 +0000 [thread overview]
Message-ID: <165055201268.27677.12493601547484216703.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220421132126.471515-1-maciej.fijalkowski@intel.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox•net>:
On Thu, 21 Apr 2022 15:21:24 +0200 you wrote:
> This is a follow-up to recently applied set [0] to fix the build
> warnings:
>
> error: attribute 'fallthrough' not preceding a case label or default
> label [-Werror]
>
> that Stephen has stumbled upon when merging bpf-next to linux-next.
> Apologies for these leftovers.
>
> [...]
Here is the summary with links:
- [bpf-next,1/2] ixgbe: xsk: get rid of redundant 'fallthrough'
https://git.kernel.org/bpf/bpf-next/c/e130e8d5434b
- [bpf-next,2/2] i40e: xsk: get rid of redundant 'fallthrough'
https://git.kernel.org/bpf/bpf-next/c/9d87e41a6d64
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-04-21 14:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 13:21 [PATCH bpf-next 0/2] xsk: remove reduntant 'falltrough' attributes Maciej Fijalkowski
2022-04-21 13:21 ` [PATCH bpf-next 1/2] ixgbe: xsk: get rid of redundant 'fallthrough' Maciej Fijalkowski
2022-04-21 22:23 ` Stephen Rothwell
2022-04-21 13:21 ` [PATCH bpf-next 2/2] i40e: " Maciej Fijalkowski
2022-04-21 14:40 ` 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=165055201268.27677.12493601547484216703.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=andrii@kernel$(echo .)org \
--cc=ast@kernel$(echo .)org \
--cc=bpf@vger$(echo .)kernel.org \
--cc=daniel@iogearbox$(echo .)net \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=maciej.fijalkowski@intel$(echo .)com \
--cc=magnus.karlsson@intel$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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