From: sashiko-bot@kernel.org
To: "Tariq Toukan" <tariqt@nvidia.com>
Cc: linux-rdma@vger.kernel.org
Subject: Re: [PATCH net-next] net/mlx5: Remove max_external_SFs device resource
Date: Sun, 11 Oct 2026 09:43:08 +0000 [thread overview]
Message-ID: <sashiko-outbox-167143@kernel.org> (raw)
In-Reply-To: <20261011093828.784454-1-tariqt@nvidia.com>
> From: Or Har-Toov <ohartoov@nvidia.com>
>
> The device-level max_external_SFs resource is redundant now that
> per-port max_SFs resources are registered on each PF port representor.
> Users can look up SF limits per-port directly via 'devlink port show'
> to correlate with controller number and pfnum.
>
> Signed-off-by: Or Har-Toov <ohartoov@nvidia.com>
> Reviewed-by: Shay Drori <shayd@nvidia.com>
> Reviewed-by: Moshe Shemesh <moshe@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/20261011093828.784454-1-tariqt@nvidia.com?part=1
next prev parent reply other threads:[~2026-10-11 9:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-11 9:38 [PATCH net-next] net/mlx5: Remove max_external_SFs device resource Tariq Toukan
2026-10-11 9:43 ` sashiko-bot [this message]
2026-10-12 9:40 ` netdev-bot+sashiko
2026-10-12 17:12 ` Or Har-Toov
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-167143@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;
as well as URLs for NNTP newsgroup(s).