From: Tariq Toukan <ttoukan.linux@gmail.com>
To: Tariq Toukan <tariqt@nvidia.com>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>
Cc: Saeed Mahameed <saeedm@nvidia.com>,
Leon Romanovsky <leon@kernel.org>,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [pull-request] mlx5-next updates 2025-07-03
Date: Fri, 4 Jul 2025 07:55:20 +0300 [thread overview]
Message-ID: <15c4c8d9-e9d8-4c4c-ad13-c734bbb04bb3@gmail.com> (raw)
In-Reply-To: <1751574385-24672-1-git-send-email-tariqt@nvidia.com>
On 03/07/2025 23:26, Tariq Toukan wrote:
> Hi,
>
> The following pull-request contains common mlx5 updates
> for your *net-next* tree.
> Please pull and let me know of any problem.
>
> Regards,
> Tariq
>
This is V2, previous PR submitted by Mark:
https://lore.kernel.org/all/e7a83ea5-d70b-4c37-8068-a73293b51262@nvidia.com/
V2:
- add a bug fix for the fs patch.
> ----------------------------------------------------------------
>
> The following changes since commit e04c78d86a9699d136910cfc0bdcf01087e3267e:
>
> Linux 6.16-rc2 (2025-06-15 13:49:41 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mellanox/linux.git 02943ac2f6fb
>
> for you to fetch changes up to 02943ac2f6fbba8fc5e57c57e7cbc2d7c67ebf0d:
>
> net/mlx5: fs, fix RDMA TRANSPORT init cleanup flow (2025-07-02 14:08:18 -0400)
>
> ----------------------------------------------------------------
> Dragos Tatulea (2):
> net/mlx5: Small refactor for general object capabilities
> net/mlx5: Add IFC bits for PCIe Congestion Event object
>
> Patrisious Haddad (2):
> net/mlx5: fs, add multiple prios to RDMA TRANSPORT steering domain
> net/mlx5: fs, fix RDMA TRANSPORT init cleanup flow
>
> drivers/net/ethernet/mellanox/mlx5/core/fs_core.c | 44 ++++++++++++---
> include/linux/mlx5/fs.h | 2 +-
> include/linux/mlx5/mlx5_ifc.h | 67 +++++++++++++++++++----
> 3 files changed, 93 insertions(+), 20 deletions(-)
>
next prev parent reply other threads:[~2025-07-04 4:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 20:26 [pull-request] mlx5-next updates 2025-07-03 Tariq Toukan
2025-07-04 4:55 ` Tariq Toukan [this message]
2025-07-07 23:59 ` Jakub Kicinski
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=15c4c8d9-e9d8-4c4c-ad13-c734bbb04bb3@gmail.com \
--to=ttoukan.linux@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--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.