From: Tariq Toukan <tariqt@nvidia.com>
To: Saeed Mahameed <saeed@kernel.org>, Leon Romanovsky <leon@kernel.org>
Cc: 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>,
Gal Pressman <gal@nvidia.com>,
"Saeed Mahameed" <saeedm@nvidia.com>,
Tariq Toukan <tariqt@nvidia.com>, Mark Bloch <mbloch@nvidia.com>,
<netdev@vger.kernel.org>, <linux-rdma@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: [PATCH mlx5-next 0/3] mlx5-next updates 2025-07-17
Date: Thu, 17 Jul 2025 09:48:12 +0300 [thread overview]
Message-ID: <1752734895-257735-1-git-send-email-tariqt@nvidia.com> (raw)
Hi,
This series contains mlx5 shared updates as preparation for upcoming
features.
Regards,
Tariq
Jianbo Liu (1):
net/mlx5: Add IFC bits to support RSS for IPSec offload
Oren Sidi (2):
net/mlx5: Add IFC bits and enums for buf_ownership
net/mlx5: Expose cable_length field in PFCC register
.../mellanox/mlx5/core/steering/hws/definer.c | 13 +++--
include/linux/mlx5/mlx5_ifc.h | 58 ++++++++++++++-----
2 files changed, 53 insertions(+), 18 deletions(-)
base-commit: cd1746cb6555a2238c4aae9f9d60b637a61bf177
--
2.31.1
next reply other threads:[~2025-07-17 6:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 6:48 Tariq Toukan [this message]
2025-07-17 6:48 ` [PATCH mlx5-next 1/3] net/mlx5: Add IFC bits to support RSS for IPSec offload Tariq Toukan
2025-07-17 6:48 ` [PATCH mlx5-next 2/3] net/mlx5: Add IFC bits and enums for buf_ownership Tariq Toukan
2025-07-17 6:48 ` [PATCH mlx5-next 3/3] net/mlx5: Expose cable_length field in PFCC register Tariq Toukan
2025-07-20 7:03 ` [PATCH mlx5-next 0/3] mlx5-next updates 2025-07-17 Leon Romanovsky
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=1752734895-257735-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=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeed@kernel.org \
--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