[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250627164035.3ef705fa@kernel.org>
Date: Fri, 27 Jun 2025 16:40:35 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Arkadiusz Kubalewski <arkadiusz.kubalewski@...el.com>
Cc: donald.hunter@...il.com, davem@...emloft.net, edumazet@...gle.com,
pabeni@...hat.com, horms@...nel.org, vadim.fedorenko@...ux.dev,
jiri@...nulli.us, anthony.l.nguyen@...el.com, przemyslaw.kitszel@...el.com,
andrew+netdev@...n.ch, aleksandr.loktionov@...el.com, corbet@....net,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
intel-wired-lan@...ts.osuosl.org, linux-rdma@...r.kernel.org,
linux-doc@...r.kernel.org
Subject: Re: [PATCH net-next v7 0/3] dpll: add Reference SYNC feature
On Thu, 26 Jun 2025 15:52:16 +0200 Arkadiusz Kubalewski wrote:
> $ ./tools/net/ynl/pyynl/cli.py \
> --spec Documentation/netlink/specs/dpll.yaml \
> --do pin-get \
> --json '{"id":0}'
For future patches -- I think we should switch to using ynl as the CLI
name, and the --family shorthand, since the good folks at Red Hat
RPM-packaged YNL (kernel-tools).
IOW instead of the above we can say:
$ ynl --family dpll --do pin-get --json '{"id":0}'
Powered by blists - more mailing lists