From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?b?QXNiasO4cm4gU2xvdGggVMO4bm5lc2VuIDxhc3RAZmliZXJieS5uZXQ+?=@ci.codeaurora.org
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, linux-kernel@vger.kernel.org,
louis.peens@corigine.com, yanguo.li@corigine.com,
oss-drivers@corigine.com, taras.chornyi@plvision.eu,
woojung.huh@microchip.com, UNGLinuxDriver@microchip.com,
andrew@lunn.ch, f.fainelli@gmail.com, olteanv@gmail.com,
ecree.xilinx@gmail.com, jhs@mojatatu.com,
xiyou.wangcong@gmail.com, jiri@resnulli.us
Subject: Re: [PATCH net-next v3 0/4] flower: validate control flags
Date: Mon, 15 Apr 2024 09:40:28 +0000 [thread overview]
Message-ID: <171317402850.10544.12420137481628257630.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240411105302.112091-1-ast@fiberby.net>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Thu, 11 Apr 2024 10:52:53 +0000 you wrote:
> I have reviewed the flower control flags code.
> In all, but one (sfc), the flags field wasn't
> checked properly for unsupported flags.
>
> In this series I have only included a single example
> user for each helper function. Once the helpers are in,
> I will submit patches for all other drivers implementing
> flower.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/4] flow_offload: add control flag checking helpers
https://git.kernel.org/netdev/net-next/c/d11e63119432
- [net-next,v3,2/4] nfp: flower: fix check for unsupported control flags
https://git.kernel.org/netdev/net-next/c/e36245dacd2c
- [net-next,v3,3/4] net: prestera: flower: validate control flags
https://git.kernel.org/netdev/net-next/c/f8a5ea8c2a7f
- [net-next,v3,4/4] net: dsa: microchip: ksz9477: flower: validate control flags
https://git.kernel.org/netdev/net-next/c/d9a1249e715b
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:[~2024-04-15 9:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 10:52 [PATCH net-next v3 0/4] flower: validate control flags Asbjørn Sloth Tønnesen
2024-04-11 10:52 ` [PATCH net-next v3 1/4] flow_offload: add control flag checking helpers Asbjørn Sloth Tønnesen
2024-04-11 10:52 ` [PATCH net-next v3 2/4] nfp: flower: fix check for unsupported control flags Asbjørn Sloth Tønnesen
2024-04-11 10:52 ` [PATCH net-next v3 3/4] net: prestera: flower: validate " Asbjørn Sloth Tønnesen
2024-04-11 10:52 ` [PATCH net-next v3 4/4] net: dsa: microchip: ksz9477: " Asbjørn Sloth Tønnesen
2024-04-15 9: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=171317402850.10544.12420137481628257630.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?b?QXNiasO4cm4gU2xvdGggVMO4bm5lc2VuIDxhc3RAZmliZXJieS5uZXQ+?=@ci.codeaurora.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=louis.peens@corigine.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=oss-drivers@corigine.com \
--cc=pabeni@redhat.com \
--cc=taras.chornyi@plvision.eu \
--cc=woojung.huh@microchip.com \
--cc=xiyou.wangcong@gmail.com \
--cc=yanguo.li@corigine.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