From: Przemek Kitszel <przemyslaw.kitszel@intel.com>
To: Tariq Toukan <tariqt@nvidia.com>,
Leon Romanovsky <leon@kernel.org>, <linux-rdma@vger.kernel.org>,
Mark Bloch <mbloch@nvidia.com>, <netdev@vger.kernel.org>,
Saeed Mahameed <saeedm@nvidia.com>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>, Gal Pressman <gal@nvidia.com>,
Jakub Kicinski <kuba@kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Moshe Shemesh <moshe@nvidia.com>, Nimrod Oren <noren@nvidia.com>,
Or Har-Toov <ohartoov@nvidia.com>,
Paolo Abeni <pabeni@redhat.com>, Shay Drory <shayd@nvidia.com>
Subject: Re: [PATCH mlx5-next 0/2] mlx5-next updates 2026-10-05
Date: Mon, 5 Oct 2026 15:29:15 +0200 [thread overview]
Message-ID: <ae31c9f2-eb4e-4d9e-8ea5-27364e389be5@intel.com> (raw)
In-Reply-To: <20261005084047.237081-1-tariqt@nvidia.com>
On 10/5/26 10:40 AM, Tariq Toukan wrote:
> Hi,
>
> This series contains mlx5 shared updates as preparation for upcoming
> features.
>
> Regards,
> Tariq
>
> Or Har-Toov (1):
> net/mlx5: Add cap_tx_speed and effective_tx_speed support to IFC
>
> Shay Drory (1):
> net/mlx5: IFC, Add capability bits for virtual LAG
>
> include/linux/mlx5/mlx5_ifc.h | 16 +++++++++++++---
> 1 file changed, 13 insertions(+), 3 deletions(-)
>
>
> base-commit: 00290b9ff59ef47b990d26a6b1a8b2ea6dedf5e9
my understanding is that you should at least link to the
actual code using the new stuff
next prev parent reply other threads:[~2026-10-05 13:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 8:40 Tariq Toukan
2026-10-05 8:40 ` [PATCH mlx5-next 1/2] net/mlx5: Add cap_tx_speed and effective_tx_speed support to IFC Tariq Toukan
2026-10-05 8:40 ` [PATCH mlx5-next 2/2] net/mlx5: IFC, Add capability bits for virtual LAG Tariq Toukan
2026-10-05 13:29 ` Przemek Kitszel [this message]
2026-10-05 21:24 ` [PATCH mlx5-next 0/2] mlx5-next updates 2026-10-05 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=ae31c9f2-eb4e-4d9e-8ea5-27364e389be5@intel.com \
--to=przemyslaw.kitszel@intel.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=noren@nvidia.com \
--cc=ohartoov@nvidia.com \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=shayd@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
all inboxes | Powered by JetHome®