From: Stephen Hemminger <stephen@networkplumber.org>
To: Jiri Pirko <jiri@resnulli.us>
Cc: Saeed Mahameed <saeedm@nvidia.com>,
Saeed Mahameed <saeed@kernel.org>,
David Ahern <dsahern@gmail.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH iproute2-next] bash-completion: devlink: fix port param name show completion
Date: Tue, 19 Nov 2024 08:45:47 -0800 [thread overview]
Message-ID: <20241119084547.4285a0dd@hermes.local> (raw)
In-Reply-To: <ZzhQjYrQmR5XHcLA@nanopsycho.orion>
On Sat, 16 Nov 2024 08:58:05 +0100
Jiri Pirko <jiri@resnulli.us> wrote:
> Fri, Nov 15, 2024 at 07:44:01PM CET, saeedm@nvidia.com wrote:
> >On 15 Nov 13:58, Jiri Pirko wrote:
> >> Fri, Nov 15, 2024 at 06:58:48AM CET, saeed@kernel.org wrote:
> >> > From: Saeed Mahameed <saeedm@nvidia.com>
> >> >
> >> > Port param names are found with "devlink port param show", and not
> >> > "devlink param show", fix that.
> >> >
> >> > Port dev name can be a netdev, so find the actual port dev before
> >> > querying "devlink port params show | jq '... [$dev] ...'",
> >> > since "devlink port params show" doesn't return the netdev name,
> >> > but the actual port dev name.
> >> >
> >> > Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
> >> > ---
> >> > bash-completion/devlink | 11 ++++++++++-
> >> > 1 file changed, 10 insertions(+), 1 deletion(-)
> >> >
> >> > diff --git a/bash-completion/devlink b/bash-completion/devlink
> >> > index 52dc82b3..ac5ea62c 100644
> >> > --- a/bash-completion/devlink
> >> > +++ b/bash-completion/devlink
> >> > @@ -43,6 +43,15 @@ _devlink_direct_complete()
> >> > value=$(devlink -j dev param show 2>/dev/null \
> >> > | jq ".param[\"$dev\"][].name")
> >> > ;;
> >> > + port_param_name)
> >> > + dev=${words[4]}
> >> > + # dev could be a port or a netdev so find the port
> >> > + portdev=$(devlink -j port show dev $dev 2>/dev/null \
> >> > + | jq '.port as $ports | $ports | keys[] as $keys | keys[0] ')
> >> > +
> >> > + value=$(devlink -j port param show 2>/dev/null \
> >>
> >> As you only care about params for specific port, you should pass it as
> >> cmdline option here. And you can pass netdev directly, devlink knows how
> >> to handle that. If I'm not missing anything in the code, should work
> >> right now.
> >>
> >
> >Nope doesn't work:
> >
> >$ devlink -j port param show mlx5_1
> >Parameter name expected.
> >
> >$ devlink -j port param show auxiliary/mlx5_core.eth.0/65535
> >Parameter name expected.
>
> Okay, so fix it :)
Holding off on applying this until some conclusion is reached.
prev parent reply other threads:[~2024-11-19 16:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 5:58 [PATCH iproute2-next] bash-completion: devlink: fix port param name show completion Saeed Mahameed
2024-11-15 12:58 ` Jiri Pirko
2024-11-15 18:44 ` Saeed Mahameed
2024-11-16 7:58 ` Jiri Pirko
2024-11-19 16:45 ` Stephen Hemminger [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=20241119084547.4285a0dd@hermes.local \
--to=stephen@networkplumber.org \
--cc=dsahern@gmail.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=saeed@kernel.org \
--cc=saeedm@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.