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,
wenjuan.geng@corigine.com
Subject: Re: [PATCH net-next] nfp: flower: support case of match on ct_state(0/0x3f)
Date: Thu, 25 Aug 2022 09:20:14 +0000 [thread overview]
Message-ID: <166141921490.14119.14804004118564255552.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220823090122.403631-1-simon.horman@corigine.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 23 Aug 2022 11:01:22 +0200 you wrote:
> From: Wenjuan Geng <wenjuan.geng@corigine.com>
>
> is_post_ct_flow() function will process only ct_state ESTABLISHED,
> then offload_pre_check() function will check FLOW_DISSECTOR_KEY_CT flag.
> When config tc filter match ct_state(0/0x3f), dissector->used_keys
> with FLOW_DISSECTOR_KEY_CT bit, function offload_pre_check() will
> return false, so not offload. This is a special case that can be handled
> safely.
>
> [...]
Here is the summary with links:
- [net-next] nfp: flower: support case of match on ct_state(0/0x3f)
https://git.kernel.org/netdev/net-next/c/ff763011ee7b
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-08-25 9:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 9:01 [PATCH net-next] nfp: flower: support case of match on ct_state(0/0x3f) Simon Horman
2022-08-25 9:20 ` 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=166141921490.14119.14804004118564255552.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@corigine.com \
--cc=pabeni@redhat.com \
--cc=simon.horman@corigine.com \
--cc=wenjuan.geng@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).