From: patchwork-bot+netdevbpf@kernel.org
To: Simon Horman <simon.horman@corigine.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, oss-drivers@corigine.com,
hui.zhou@corigine.com, ziyang.chen@corigine.com
Subject: Re: [PATCH net-next 0/3] nfp: flower: police validation and ct enhancements
Date: Tue, 20 Sep 2022 20:40:18 +0000 [thread overview]
Message-ID: <166370641892.8632.8260909998214462880.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220914160604.1740282-1-simon.horman@corigine.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 14 Sep 2022 17:06:01 +0100 you wrote:
> Hi,
>
> this series enhances the flower hardware offload
> facility provided by the nfp driver.
>
> 1. Add validation of police actions created independently of flows
>
> [...]
Here is the summary with links:
- [net-next,1/3] nfp: flower: add validation of for police actions which are independent of flows
https://git.kernel.org/netdev/net-next/c/9f1a948fd6ef
- [net-next,2/3] nfp: flower: support hw offload for ct nat action
https://git.kernel.org/netdev/net-next/c/5cee92c6f57a
- [net-next,3/3] nfp: flower: support vlan action in pre_ct
https://git.kernel.org/netdev/net-next/c/742b7072764a
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-09-20 20:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 16:06 [PATCH net-next 0/3] nfp: flower: police validation and ct enhancements Simon Horman
2022-09-14 16:06 ` [PATCH net-next 1/3] nfp: flower: add validation of for police actions which are independent of flows Simon Horman
2022-09-14 16:06 ` [PATCH net-next 2/3] nfp: flower: support hw offload for ct nat action Simon Horman
2022-09-14 16:06 ` [PATCH net-next 3/3] nfp: flower: support vlan action in pre_ct Simon Horman
2022-09-20 20: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=166370641892.8632.8260909998214462880.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=hui.zhou@corigine.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@corigine.com \
--cc=pabeni@redhat.com \
--cc=simon.horman@corigine.com \
--cc=ziyang.chen@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;
as well as URLs for NNTP newsgroup(s).