Subject: Re: [patch net-next] dpll: spec: use proper enum for pin capabilities attribute

From: Jiri Pirko <[email-masked]>
Date: Wed, 6 Mar 2024 16:25:34 +0100

Wed, Mar 06, 2024 at 01:07:39PM CET, [email-masked] wrote:
>From: Jiri Pirko <[email-masked]>
>
>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 <[email-masked]>

Note that netdev/cc_maintainers fails as I didn't cc [email-masked]
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?