From: sashiko-bot@kernel.org
To: "Tariq Toukan" <tariqt@nvidia.com>
Cc: linux-rdma@vger.kernel.org
Subject: Re: [PATCH mlx5-next 2/4] net/mlx5: Add function_id_type for enable/disable_hca cmds
Date: Fri, 30 Oct 2026 04:53:40 +0000 [thread overview]
Message-ID: <sashiko-outbox-190336@kernel.org> (raw)
In-Reply-To: <20260428053851.220089-3-tariqt@nvidia.com>
> From: Moshe Shemesh <moshe@nvidia.com>
>
> Add a function_id_type field to the enable_hca and disable_hca command
> input layouts in mlx5_ifc.h to allow using vhca_id as the function index
> instead of function_id. The new field support by firmware is indicated
> by the function_id_type_vhca_id capability bit, which is already exposed
> in hca caps.
>
> Signed-off-by: Moshe Shemesh <moshe@nvidia.com>
> Signed-off-by: Tariq Toukan <tariqt@nvidia.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260428053851.220089-1-tariqt@nvidia.com?part=2
next prev parent reply other threads:[~2026-10-30 4:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 5:38 [PATCH mlx5-next 0/4] mlx5-next updates 2026-04-28 Tariq Toukan
2026-04-28 5:38 ` [PATCH mlx5-next 1/4] mlx5: Rename the vport number enums for host PF and VF Tariq Toukan
2026-04-28 5:38 ` [PATCH mlx5-next 2/4] net/mlx5: Add function_id_type for enable/disable_hca cmds Tariq Toukan
2026-10-30 4:53 ` sashiko-bot [this message]
2026-04-28 5:38 ` [PATCH mlx5-next 3/4] net/mlx5: Remove unused host_sf_enable field Tariq Toukan
2026-10-30 4:53 ` sashiko-bot
2026-04-28 5:38 ` [PATCH mlx5-next 4/4] net/mlx5: Extend query_esw_functions output for multi-function support Tariq Toukan
2026-10-30 4:53 ` sashiko-bot
2026-04-29 20:28 ` [PATCH mlx5-next 0/4] mlx5-next updates 2026-04-28 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=sashiko-outbox-190336@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox