From: patchwork-bot+netdevbpf@kernel.org
To: Ido Schimmel <idosch@nvidia.com>
Cc: netdev@vger.kernel.org, stephen@networkplumber.org,
dsahern@kernel.org, jiri@nvidia.com, petrm@nvidia.com
Subject: Re: [PATCH iproute2] devlink: Fix resource show output
Date: Tue, 20 Jan 2026 23:30:04 +0000 [thread overview]
Message-ID: <176895180486.650765.4216703988085899594.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260115115004.863685-1-idosch@nvidia.com>
Hello:
This patch was applied to iproute2/iproute2.git (main)
by Stephen Hemminger <stephen@networkplumber.org>:
On Thu, 15 Jan 2026 13:50:04 +0200 you wrote:
> When the user asks to show device resources, devlink first queries the
> device's dpipe tables so that it will be able to show the association
> between resources and dpipe tables.
>
> In this flow, 'ctx->resources' is always NULL as resources have yet to
> be retrieved. As a result, the dpipe tables are not associated with a
> resource identifier and the resource show command does not show any
> dpipe tables:
>
> [...]
Here is the summary with links:
- [iproute2] devlink: Fix resource show output
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=f2b24087e154
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-01-20 23:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 11:50 [PATCH iproute2] devlink: Fix resource show output Ido Schimmel
2026-01-20 23:30 ` 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=176895180486.650765.4216703988085899594.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=dsahern@kernel.org \
--cc=idosch@nvidia.com \
--cc=jiri@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=petrm@nvidia.com \
--cc=stephen@networkplumber.org \
/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.