From: Leon Romanovsky <leon@kernel.org>
To: linux-rdma@vger.kernel.org, Mark Bloch <mbloch@nvidia.com>,
netdev@vger.kernel.org, Saeed Mahameed <saeedm@nvidia.com>,
Tariq Toukan <tariqt@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: Sun, 11 Oct 2026 07:06:48 -0400 [thread overview]
Message-ID: <179171680884.3031064.1016849448446915116.b4-ty@kernel.org> (raw)
In-Reply-To: <20261005084047.237081-1-tariqt@nvidia.com>
On Mon, 05 Oct 2026 11:40:45 +0300, Tariq Toukan wrote:
> 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
>
> [...]
Applied, thanks!
[1/2] net/mlx5: Add cap_tx_speed and effective_tx_speed support to IFC
https://git.kernel.org/rdma/rdma/c/4c5679222f6b9b
[2/2] net/mlx5: IFC, Add capability bits for virtual LAG
https://git.kernel.org/rdma/rdma/c/41de84543574f2
Best regards,
--
Leon Romanovsky <leon@kernel.org>
prev parent reply other threads:[~2026-10-11 11:06 UTC|newest]
Thread overview: 6+ 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 ` [PATCH mlx5-next 0/2] mlx5-next updates 2026-10-05 Przemek Kitszel
2026-10-05 21:24 ` Jakub Kicinski
2026-10-11 11:06 ` Leon Romanovsky [this message]
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=179171680884.3031064.1016849448446915116.b4-ty@kernel.org \
--to=leon@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=kuba@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®