From: Tariq Toukan <tariqt@nvidia.com>
To: 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: Leon Romanovsky <leon@kernel.org>,
Saeed Mahameed <saeedm@nvidia.com>,
Tariq Toukan <tariqt@nvidia.com>, Mark Bloch <mbloch@nvidia.com>,
<linux-rdma@vger.kernel.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Moshe Shemesh <moshe@nvidia.com>,
"Gal Pressman" <gal@nvidia.com>
Subject: [pull-request] mlx5-next updates 2025-09-28
Date: Mon, 29 Sep 2025 00:13:09 +0300 [thread overview]
Message-ID: <1759093989-841873-1-git-send-email-tariqt@nvidia.com> (raw)
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
----------------------------------------------------------------
The following changes since commit a3d076b0567e729d5f21a95525c4d096b1f59e79:
net/mlx5: Add uar access and odp page fault counters (2025-09-18 05:32:22 -0400)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mellanox/linux.git tags/mlx5-next-lag
for you to fetch changes up to 137d1a6355131457723b51a34192320d93d15654:
net/mlx5: IFC add balance ID and LAG per MP group bits (2025-09-28 03:36:36 -0400)
----------------------------------------------------------------
Mark Bloch (1):
net/mlx5: IFC add balance ID and LAG per MP group bits
Tariq Toukan (1):
net/mlx5: Add IFC bit for TIR/SQ order capability
include/linux/mlx5/mlx5_ifc.h | 11 ++++++++---
1 file changed, 8 insertions(+), 3 deletions(-)
next reply other threads:[~2025-09-28 21:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-28 21:13 Tariq Toukan [this message]
2025-09-30 2:00 ` patchwork-bot+netdevbpf
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=1759093989-841873-1-git-send-email-tariqt@nvidia.com \
--to=tariqt@nvidia.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=moshe@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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
all inboxes | Powered by JetHome®