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>, Jason Gunthorpe <jgg@ziepe.ca>,
"Saeed Mahameed" <saeedm@nvidia.com>,
Tariq Toukan <tariqt@nvidia.com>, <linux-rdma@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
Mark Bloch <mbloch@nvidia.com>
Subject: [pull-request] mlx5-next updates 2025-07-14
Date: Mon, 14 Jul 2025 11:22:37 +0300 [thread overview]
Message-ID: <1752481357-34780-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 70f238c902b8c0461ae6fbb8d1a0bbddc4350eea:
net/mlx5: Check device memory pointer before usage (2025-07-02 14:08:23 -0400)
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 cd1746cb6555a2238c4aae9f9d60b637a61bf177:
net/mlx5: IFC updates for disabled host PF (2025-07-13 03:17:30 -0400)
----------------------------------------------------------------
Carolina Jubran (1):
net/mlx5: Expose disciplined_fr_counter through HCA capabilities in mlx5_ifc
Daniel Jurgens (1):
net/mlx5: IFC updates for disabled host PF
Edward Srouji (1):
RDMA/mlx5: Fix UMR modifying of mkey page size
Michael Guralnik (1):
net/mlx5: Expose HCA capability bits for mkey max page size
drivers/infiniband/hw/mlx5/umr.c | 6 ++++--
include/linux/mlx5/device.h | 1 +
include/linux/mlx5/mlx5_ifc.h | 11 ++++++++---
3 files changed, 13 insertions(+), 5 deletions(-)
next reply other threads:[~2025-07-14 8:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 8:22 Tariq Toukan [this message]
2025-07-15 0:40 ` 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=1752481357-34780-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=jgg@ziepe.ca \
--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=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®