From: patchwork-bot+netdevbpf@kernel.org
To: Saeed Mahameed <saeed@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, maord@nvidia.com, kliteyn@nvidia.com,
saeedm@nvidia.com
Subject: Re: [net 01/11] net/mlx5: DR, Fix missing flow_source when creating multi-destination FW table
Date: Wed, 18 May 2022 11:10:13 +0000 [thread overview]
Message-ID: <165287221351.23187.1673878219095186610.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220518063427.123758-2-saeed@kernel.org>
Hello:
This series was applied to netdev/net.git (master)
by Saeed Mahameed <saeedm@nvidia.com>:
On Tue, 17 May 2022 23:34:17 -0700 you wrote:
> From: Maor Dickman <maord@nvidia.com>
>
> In order to support multiple destination FTEs with SW steering
> FW table is created with single FTE with multiple actions and
> SW steering rule forward to it. When creating this table, flow
> source isn't set according to the original FTE.
>
> [...]
Here is the summary with links:
- [net,01/11] net/mlx5: DR, Fix missing flow_source when creating multi-destination FW table
https://git.kernel.org/netdev/net/c/2c5fc6cd269a
- [net,02/11] net/mlx5: Initialize flow steering during driver probe
https://git.kernel.org/netdev/net/c/b33886971dbc
- [net,03/11] net/mlx5: DR, Ignore modify TTL on RX if device doesn't support it
https://git.kernel.org/netdev/net/c/785d7ed29551
- [net,04/11] net/mlx5e: Wrap mlx5e_trap_napi_poll into rcu_read_lock
https://git.kernel.org/netdev/net/c/379169740b0a
- [net,05/11] net/mlx5e: Block rx-gro-hw feature in switchdev mode
https://git.kernel.org/netdev/net/c/15a5078cab30
- [net,06/11] net/mlx5e: Properly block LRO when XDP is enabled
https://git.kernel.org/netdev/net/c/cf6e34c8c22f
- [net,07/11] net/mlx5e: Properly block HW GRO when XDP is enabled
https://git.kernel.org/netdev/net/c/b0617e7b3500
- [net,08/11] net/mlx5e: Remove HW-GRO from reported features
https://git.kernel.org/netdev/net/c/6bbd723035ba
- [net,09/11] net/mlx5e: CT: Fix support for GRE tuples
https://git.kernel.org/netdev/net/c/8e1dcf499a67
- [net,10/11] net/mlx5e: CT: Fix setting flow_source for smfs ct tuples
https://git.kernel.org/netdev/net/c/04c551bad371
- [net,11/11] net/mlx5: Drain fw_reset when removing device
https://git.kernel.org/netdev/net/c/16d42d313350
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-05-18 11:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 6:34 [pull request][net 00/11] mlx5 fixes 2022-05-17 Saeed Mahameed
2022-05-18 6:34 ` [net 01/11] net/mlx5: DR, Fix missing flow_source when creating multi-destination FW table Saeed Mahameed
2022-05-18 11:10 ` patchwork-bot+netdevbpf [this message]
2022-05-18 6:34 ` [net 02/11] net/mlx5: Initialize flow steering during driver probe Saeed Mahameed
2022-05-18 6:34 ` [net 03/11] net/mlx5: DR, Ignore modify TTL on RX if device doesn't support it Saeed Mahameed
2022-05-18 6:34 ` [net 04/11] net/mlx5e: Wrap mlx5e_trap_napi_poll into rcu_read_lock Saeed Mahameed
2022-05-18 6:34 ` [net 05/11] net/mlx5e: Block rx-gro-hw feature in switchdev mode Saeed Mahameed
2022-05-18 6:34 ` [net 06/11] net/mlx5e: Properly block LRO when XDP is enabled Saeed Mahameed
2022-05-18 6:34 ` [net 07/11] net/mlx5e: Properly block HW GRO " Saeed Mahameed
2022-05-18 6:34 ` [net 08/11] net/mlx5e: Remove HW-GRO from reported features Saeed Mahameed
2022-05-18 6:34 ` [net 09/11] net/mlx5e: CT: Fix support for GRE tuples Saeed Mahameed
2022-05-18 6:34 ` [net 10/11] net/mlx5e: CT: Fix setting flow_source for smfs ct tuples Saeed Mahameed
2022-05-18 6:34 ` [net 11/11] net/mlx5: Drain fw_reset when removing device Saeed Mahameed
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=165287221351.23187.1673878219095186610.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kliteyn@nvidia.com \
--cc=kuba@kernel.org \
--cc=maord@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeed@kernel.org \
--cc=saeedm@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).