From: patchwork-bot+netdevbpf@kernel.org
To: Boris Sukholitko <boris.sukholitko@broadcom.com>
Cc: netdev@vger.kernel.org, jhs@mojatatu.com, jiri@resnulli.us,
xiyou.wangcong@gmail.com, davem@davemloft.net, kuba@kernel.org,
olteanv@gmail.com, vadym.kochan@plvision.eu,
ilya.lifshits@broadcom.com
Subject: Re: [PATCH net-next] Revert "net/sched: cls_flower: Remove match on n_proto"
Date: Mon, 21 Jun 2021 21:50:05 +0000 [thread overview]
Message-ID: <162431220514.17422.16259635300639529077.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210621092429.10043-1-boris.sukholitko@broadcom.com>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Mon, 21 Jun 2021 12:24:29 +0300 you wrote:
> This reverts commit 0dca2c7404a938cb10c85d0515cee40ed5348788.
>
> The commit in question breaks hardware offload of flower filters.
>
> Quoting Vladimir Oltean <olteanv@gmail.com>:
>
> fl_hw_replace_filter() and fl_reoffload() create a struct
> flow_cls_offload with a rule->match.mask member derived from the mask
> of the software classifier: &f->mask->key - that same mask that is used
> for initializing the flow dissector keys, and the one from which Boris
> removed the basic.n_proto member because it was bothering him.
>
> [...]
Here is the summary with links:
- [net-next] Revert "net/sched: cls_flower: Remove match on n_proto"
https://git.kernel.org/netdev/net-next/c/6d5516177d3b
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:[~2021-06-21 21:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 9:24 [PATCH net-next] Revert "net/sched: cls_flower: Remove match on n_proto" Boris Sukholitko
2021-06-21 10:11 ` Vladimir Oltean
2021-06-21 21:50 ` 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=162431220514.17422.16259635300639529077.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=boris.sukholitko@broadcom.com \
--cc=davem@davemloft.net \
--cc=ilya.lifshits@broadcom.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=vadym.kochan@plvision.eu \
--cc=xiyou.wangcong@gmail.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).