From: patchwork-bot+netdevbpf@kernel.org
To: Tariq Toukan <tariqt@nvidia.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, netdev@vger.kernel.org, pabeni@redhat.com,
cjubran@nvidia.com, cmi@nvidia.com, cratiu@nvidia.com,
gal@nvidia.com, jiri@resnulli.us, corbet@lwn.net,
kees@kernel.org, leon@kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
mbloch@nvidia.com, moshe@nvidia.com, ohartoov@nvidia.com,
rdunlap@infradead.org, saeedm@nvidia.com, shayd@nvidia.com,
skhan@linuxfoundation.org, horms@kernel.org
Subject: Re: [PATCH net-next] net/mlx5: Remove max_external_SFs device resource
Date: Sat, 17 Oct 2026 00:50:08 +0000 [thread overview]
Message-ID: <179219820801.1034269.1188616668560907139.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261011093828.784454-1-tariqt@nvidia.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 11 Oct 2026 12:38:28 +0300 you wrote:
> 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.
>
> [...]
Here is the summary with links:
- [net-next] net/mlx5: Remove max_external_SFs device resource
https://git.kernel.org/netdev/net-next/c/001e9181ada8
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-10-17 0:50 UTC|newest]
Thread overview: 6+ 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
2026-10-12 9:40 ` netdev-bot+sashiko
2026-10-12 17:12 ` Or Har-Toov
2026-10-16 18:36 ` Simon Horman
2026-10-17 0:50 ` patchwork-bot+netdevbpf [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=179219820801.1034269.1188616668560907139.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=cjubran@nvidia.com \
--cc=cmi@nvidia.com \
--cc=corbet@lwn.net \
--cc=cratiu@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=gal@nvidia.com \
--cc=horms@kernel.org \
--cc=jiri@resnulli.us \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-doc@vger.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=ohartoov@nvidia.com \
--cc=pabeni@redhat.com \
--cc=rdunlap@infradead.org \
--cc=saeedm@nvidia.com \
--cc=shayd@nvidia.com \
--cc=skhan@linuxfoundation.org \
--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