public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: netdev@vger.kernel.org
Cc: kuba@kernel.org, pabeni@redhat.com, davem@davemloft.net,
	edumazet@google.com, arkadiusz.kubalewski@intel.com,
	vadim.fedorenko@linux.dev
Subject: Re: [patch net-next] dpll: spec: use proper enum for pin capabilities attribute
Date: Wed, 6 Mar 2024 16:25:34 +0100	[thread overview]
Message-ID: <ZeiK7gDRUZYA8378@nanopsycho> (raw)
In-Reply-To: <20240306120739.1447621-1-jiri@resnulli.us>

Wed, Mar 06, 2024 at 01:07:39PM CET, jiri@resnulli.us wrote:
>From: Jiri Pirko <jiri@nvidia.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@nvidia.com>

Note that netdev/cc_maintainers fails as I didn't cc michal.michalik@intel.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?

  reply	other threads:[~2024-03-06 15:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-06 12:07 [patch net-next] dpll: spec: use proper enum for pin capabilities attribute Jiri Pirko
2024-03-06 15:25 ` Jiri Pirko [this message]
2024-03-06 15:34   ` Jakub Kicinski
2024-03-13 14:26     ` Jakub Kicinski
2024-03-13 14:58       ` Jiri Pirko
2024-03-13 15:31         ` Jakub Kicinski
2024-03-14  8:42           ` Jiri Pirko
2024-03-07  4:27 ` Jakub Kicinski
2024-03-08  5:00 ` patchwork-bot+netdevbpf

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=ZeiK7gDRUZYA8378@nanopsycho \
    --to=jiri@resnulli.us \
    --cc=arkadiusz.kubalewski@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=vadim.fedorenko@linux.dev \
    /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