From: patchwork-bot+netdevbpf@kernel.org
To: Saeed Mahameed <saeed@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, saeedm@nvidia.com, netdev@vger.kernel.org,
tariqt@nvidia.com, jianbol@nvidia.com, vladbu@nvidia.com
Subject: Re: [PATCH net 1/2] net/mlx5e: Clear mirred devices array if the rule is split
Date: Wed, 06 Sep 2023 05:20:22 +0000 [thread overview]
Message-ID: <169397762259.26821.10788455717619544046.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230905174846.24124-1-saeed@kernel.org>
Hello:
This series was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Tue, 5 Sep 2023 10:48:45 -0700 you wrote:
> From: Jianbo Liu <jianbol@nvidia.com>
>
> In the cited commit, the mirred devices are recorded and checked while
> parsing the actions. In order to avoid system crash, the duplicate
> action in a single rule is not allowed.
>
> But the rule is actually break down into several FTEs in different
> tables, for either mirroring, or the specified types of actions which
> use post action infrastructure.
>
> [...]
Here is the summary with links:
- [net,1/2] net/mlx5e: Clear mirred devices array if the rule is split
https://git.kernel.org/netdev/net/c/b7558a77529f
- [net,2/2] mlx5/core: E-Switch, Create ACL FT for eswitch manager in switchdev mode
https://git.kernel.org/netdev/net/c/344134609a56
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:[~2023-09-06 5:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 17:48 [PATCH net 1/2] net/mlx5e: Clear mirred devices array if the rule is split Saeed Mahameed
2023-09-05 17:48 ` [PATCH net 2/2] mlx5/core: E-Switch, Create ACL FT for eswitch manager in switchdev mode Saeed Mahameed
2023-09-06 5: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=169397762259.26821.10788455717619544046.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jianbol@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeed@kernel.org \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.com \
--cc=vladbu@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 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).