From: sashiko-bot@kernel.org
To: "Tariq Toukan" <tariqt@nvidia.com>
Cc: linux-rdma@vger.kernel.org
Subject: Re: [PATCH mlx5-next 1/2] net/mlx5: Add cap_tx_speed and effective_tx_speed support to IFC
Date: Mon, 05 Oct 2026 08:46:38 +0000 [thread overview]
Message-ID: <20261005084639.414141F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20261005084047.237081-2-tariqt@nvidia.com>
> From: Or Har-Toov <ohartoov@nvidia.com>
>
> Introduce the cap_tx_speed and effective_tx_speed fields to the query
> and modify_vport_state structures.
>
> Add the esw_vport_state_cap_tx_speed and
> esw_vport_state_effective_tx_speed capability bits, indicating the
> firmware supports modifying the cap_tx_speed and effective_tx_speed
> fields, via the MODIFY_VPORT_STATE command.
>
> Signed-off-by: Or Har-Toov <ohartoov@nvidia.com>
> Reviewed-by: Mark Bloch <mbloch@nvidia.com>
> Reviewed-by: Nimrod Oren <noren@nvidia.com>
> Signed-off-by: Tariq Toukan <tariqt@nvidia.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261005084047.237081-1-tariqt@nvidia.com?part=1
next prev parent reply other threads:[~2026-10-05 8:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 8:40 [PATCH mlx5-next 0/2] mlx5-next updates 2026-10-05 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:46 ` sashiko-bot [this message]
2026-10-05 8:40 ` [PATCH mlx5-next 2/2] net/mlx5: IFC, Add capability bits for virtual LAG Tariq Toukan
2026-10-05 8:46 ` sashiko-bot
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
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=20261005084639.414141F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.