From: Mark Bloch <mbloch@nvidia.com>
To: "David S. Miller\"" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Simon Horman <horms@kernel.org>
Cc: Leon Romanovsky <leonro@nvidia.com>,
Tariq Toukan <tariqt@nvidia.com>,
netdev@vger.kernel.org,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Patrisious Haddad <phaddad@nvidia.com>,
Dragos Tatulea <dtatulea@nvidia.com>,
Saeed Mahameed <saeedm@nvidia.com>
Subject: [pull-request] mlx5-next updates 2025-06-25
Date: Wed, 25 Jun 2025 17:41:54 +0300 [thread overview]
Message-ID: <e7a83ea5-d70b-4c37-8068-a73293b51262@nvidia.com> (raw)
Hi,
This pull request has three patches for net-next/main. Containing
general updates for the mlx5 driver. The two patches by Dragos
are preparation for an upcoming series that will expose PCI counters
for mlx5 devices.
Regards,
Mark
----------------------------------------------------------------
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 mlx5-next
for you to fetch changes up to 1f6da56679d33c733aaee929fd9af962ad66edbd:
net/mlx5: Add IFC bits for PCIe Congestion Event object (2025-06-25 07:34:27 -0400)
----------------------------------------------------------------
Dragos Tatulea (2):
net/mlx5: Small refactor for general object capabilities
net/mlx5: Add IFC bits for PCIe Congestion Event object
Patrisious Haddad (1):
net/mlx5: fs, add multiple prios to RDMA TRANSPORT steering domain
drivers/net/ethernet/mellanox/mlx5/core/fs_core.c | 30 ++++++++++++++++++++++--------
include/linux/mlx5/fs.h | 2 +-
include/linux/mlx5/mlx5_ifc.h | 67 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++-----------
3 files changed, 79 insertions(+), 20 deletions(-)
reply other threads:[~2025-06-25 14:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=e7a83ea5-d70b-4c37-8068-a73293b51262@nvidia.com \
--to=mbloch@nvidia.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dtatulea@nvidia.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=phaddad@nvidia.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