From: Jakub Kicinski <kuba@kernel.org>
To: <saeedm@nvidia.com>
Cc: Vlad Buslov <vladbu@nvidia.com>, <davem@davemloft.net>,
<jianbol@nvidia.com>, <idosch@nvidia.com>,
<xiyou.wangcong@gmail.com>, <jhs@mojatatu.com>,
<jiri@resnulli.us>, <netdev@vger.kernel.org>, <maord@nvidia.com>
Subject: Re: [PATCH net 0/2] Fix police 'continue' action offload
Date: Tue, 5 Jul 2022 17:11:13 -0700 [thread overview]
Message-ID: <20220705171113.690109ee@kernel.org> (raw)
In-Reply-To: <20220704204405.2563457-1-vladbu@nvidia.com>
On Mon, 4 Jul 2022 22:44:03 +0200 Vlad Buslov wrote:
> TC act_police with 'continue' action had been supported by mlx5 matchall
> classifier offload implementation for some time. However, 'continue' was
> assumed implicitly and recently got broken in multiple places. Fix it in
> both TC hardware offload validation code and mlx5 driver.
Saeed, ack or should they go via your tree?
The signals are a little mixed since the tree in the subject is "net"
which makes sense but there's no ack / sob from Saeed.
next prev parent reply other threads:[~2022-07-06 0:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 20:44 [PATCH net 0/2] Fix police 'continue' action offload Vlad Buslov
2022-07-04 20:44 ` [PATCH net 1/2] net/sched: act_police: allow " Vlad Buslov
2022-07-04 20:44 ` [PATCH net 2/2] net/mlx5e: Fix matchall police parameters validation Vlad Buslov
2022-07-06 5:45 ` Saeed Mahameed
2022-07-06 0:11 ` Jakub Kicinski [this message]
2022-07-06 5:46 ` [PATCH net 0/2] Fix police 'continue' action offload Saeed Mahameed
2022-07-06 9:57 ` Vlad Buslov
2022-07-07 9:33 ` Simon Horman
2022-07-06 11:50 ` patchwork-bot+netdevbpf
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=20220705171113.690109ee@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=idosch@nvidia.com \
--cc=jhs@mojatatu.com \
--cc=jianbol@nvidia.com \
--cc=jiri@resnulli.us \
--cc=maord@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@nvidia.com \
--cc=vladbu@nvidia.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.