[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZeiK7gDRUZYA8378@nanopsycho>
Date: Wed, 6 Mar 2024 16:25:34 +0100
From: Jiri Pirko <jiri@...nulli.us>
To: netdev@...r.kernel.org
Cc: kuba@...nel.org, pabeni@...hat.com, davem@...emloft.net,
edumazet@...gle.com, arkadiusz.kubalewski@...el.com,
vadim.fedorenko@...ux.dev
Subject: Re: [patch net-next] dpll: spec: use proper enum for pin
capabilities attribute
Wed, Mar 06, 2024 at 01:07:39PM CET, jiri@...nulli.us wrote:
>From: Jiri Pirko <jiri@...dia.com>
>
>The enum is defined, however the pin capabilities attribute does
>refer to it. Add this missing enum field.
>
>This fixes ynl cli output:
>
>Example current output:
>$ sudo ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/dpll.yaml --do pin-get --json '{"id": 0}'
>{'capabilities': 4,
> ...
>Example new output:
>$ sudo ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/dpll.yaml --do pin-get --json '{"id": 0}'
>{'capabilities': {'state-can-change'},
> ...
>
>Fixes: 3badff3a25d8 ("dpll: spec: Add Netlink spec in YAML")
>Signed-off-by: Jiri Pirko <jiri@...dia.com>
Note that netdev/cc_maintainers fails as I didn't cc michal.michalik@...el.com
on purpose, as the address bounces.
Btw, do we have a way to ignore such ccs? .get_maintainer.ignore looks
like a good candidate, but is it okay to put closed emails there?
Powered by blists - more mailing lists