From: patchwork-bot+netdevbpf@kernel.org
To: Tariq Toukan <tariqt@nvidia.com>
Cc: edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
andrew+netdev@lunn.ch, davem@davemloft.net, saeedm@nvidia.com,
leon@kernel.org, mbloch@nvidia.com, cratiu@nvidia.com,
jmassar@nvidia.com, jianbol@nvidia.com, netdev@vger.kernel.org,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
gal@nvidia.com
Subject: Re: [PATCH net] net/mlx5: Do not restore destination-less TC rules
Date: Fri, 15 May 2026 01:40:09 +0000 [thread overview]
Message-ID: <177880920904.156468.11629126127893686276.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260513063302.333761-1-tariqt@nvidia.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 13 May 2026 09:33:02 +0300 you wrote:
> From: Jeroen Massar <jmassar@nvidia.com>
>
> After IPsec policy/state TX rules are added, any TC flow rule, which
> forwards packets to uplink, is modified to forward to IPsec TX tables.
> As these tables are destroyed dynamically, whenever there is no
> reference to them, the destinations of this kind of rules must be
> restored to uplink, unless there is no destination for that rule.
>
> [...]
Here is the summary with links:
- [net] net/mlx5: Do not restore destination-less TC rules
https://git.kernel.org/netdev/net/c/8d0a5af8b1ba
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:[~2026-05-15 1:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 6:33 [PATCH net] net/mlx5: Do not restore destination-less TC rules Tariq Toukan
2026-05-15 1: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=177880920904.156468.11629126127893686276.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=cratiu@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=jianbol@nvidia.com \
--cc=jmassar@nvidia.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.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.