From: patchwork-bot+netdevbpf@kernel.org
To: Tariq Toukan <tariqt@nvidia.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, andrew+netdev@lunn.ch,
netdev@vger.kernel.org, saeedm@nvidia.com, gal@nvidia.com,
leonro@nvidia.com, mbloch@nvidia.com,
przemyslaw.kitszel@intel.com
Subject: Re: [PATCH net-next V4 00/11] mlx5 misc changes 2024-12-19
Date: Mon, 23 Dec 2024 18:40:45 +0000 [thread overview]
Message-ID: <173497924501.3927205.16993887490244751404.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241219175841.1094544-1-tariqt@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 19 Dec 2024 19:58:30 +0200 you wrote:
> Hi,
>
> The first two patches by Rongwei add support for multi-host LAG. The new
> multi-host NICs provide each host with partial ports, allowing each host
> to maintain its unique LAG configuration.
>
> Patches 3-7 by Moshe, Mark and Yevgeny are enhancements and preparations
> in fs_core and HW steering, in preparation for future patchsets.
>
> [...]
Here is the summary with links:
- [net-next,V4,01/11] net/mlx5: LAG, Refactor lag logic
https://git.kernel.org/netdev/net-next/c/ddbb5ddc43ad
- [net-next,V4,02/11] net/mlx5: LAG, Support LAG over Multi-Host NICs
https://git.kernel.org/netdev/net-next/c/60d01cc468fd
- [net-next,V4,03/11] net/mlx5: fs, add counter object to flow destination
https://git.kernel.org/netdev/net-next/c/95f68e06b41b
- [net-next,V4,04/11] net/mlx5: fs, add mlx5_fs_pool API
https://git.kernel.org/netdev/net-next/c/31d1356b8fdc
- [net-next,V4,05/11] net/mlx5: fs, retry insertion to hash table on EBUSY
https://git.kernel.org/netdev/net-next/c/586face88106
- [net-next,V4,06/11] net/mlx5: HWS, no need to expose mlx5hws_send_queues_open/close
https://git.kernel.org/netdev/net-next/c/9a0155a709fa
- [net-next,V4,07/11] net/mlx5: HWS, do not initialize native API queues
https://git.kernel.org/netdev/net-next/c/429776b6019b
- [net-next,V4,08/11] net/mlx5: DR, expand SWS STE callbacks and consolidate common structs
https://git.kernel.org/netdev/net-next/c/aa90a30804a5
- [net-next,V4,09/11] net/mlx5: DR, add support for ConnectX-8 steering
https://git.kernel.org/netdev/net-next/c/4d617b57574f
- [net-next,V4,10/11] net/mlx5: Remove PTM support log message
https://git.kernel.org/netdev/net-next/c/f440d69a21f7
- [net-next,V4,11/11] net/mlx5: fs, Add support for RDMA RX steering over IB link layer
https://git.kernel.org/netdev/net-next/c/ef1749d50669
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:[~2024-12-23 18:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 17:58 [PATCH net-next V4 00/11] mlx5 misc changes 2024-12-19 Tariq Toukan
2024-12-19 17:58 ` [PATCH net-next V4 01/11] net/mlx5: LAG, Refactor lag logic Tariq Toukan
2024-12-23 18:32 ` Jakub Kicinski
2024-12-19 17:58 ` [PATCH net-next V4 02/11] net/mlx5: LAG, Support LAG over Multi-Host NICs Tariq Toukan
2024-12-19 17:58 ` [PATCH net-next V4 03/11] net/mlx5: fs, add counter object to flow destination Tariq Toukan
2024-12-19 17:58 ` [PATCH net-next V4 04/11] net/mlx5: fs, add mlx5_fs_pool API Tariq Toukan
2024-12-19 17:58 ` [PATCH net-next V4 05/11] net/mlx5: fs, retry insertion to hash table on EBUSY Tariq Toukan
2024-12-19 17:58 ` [PATCH net-next V4 06/11] net/mlx5: HWS, no need to expose mlx5hws_send_queues_open/close Tariq Toukan
2024-12-19 17:58 ` [PATCH net-next V4 07/11] net/mlx5: HWS, do not initialize native API queues Tariq Toukan
2024-12-19 17:58 ` [PATCH net-next V4 08/11] net/mlx5: DR, expand SWS STE callbacks and consolidate common structs Tariq Toukan
2024-12-19 17:58 ` [PATCH net-next V4 09/11] net/mlx5: DR, add support for ConnectX-8 steering Tariq Toukan
2024-12-19 17:58 ` [PATCH net-next V4 10/11] net/mlx5: Remove PTM support log message Tariq Toukan
2024-12-19 17:58 ` [PATCH net-next V4 11/11] net/mlx5: fs, Add support for RDMA RX steering over IB link layer Tariq Toukan
2024-12-23 18: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=173497924501.3927205.16993887490244751404.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.com \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.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 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).