netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
Cc: donald.hunter@gmail.com, davem@davemloft.net,
	edumazet@google.com, pabeni@redhat.com, horms@kernel.org,
	vadim.fedorenko@linux.dev, jiri@resnulli.us,
	anthony.l.nguyen@intel.com, przemyslaw.kitszel@intel.com,
	andrew+netdev@lunn.ch, aleksandr.loktionov@intel.com,
	corbet@lwn.net, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
	linux-rdma@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH net-next v7 0/3] dpll: add Reference SYNC feature
Date: Fri, 27 Jun 2025 16:40:35 -0700	[thread overview]
Message-ID: <20250627164035.3ef705fa@kernel.org> (raw)
In-Reply-To: <20250626135219.1769350-1-arkadiusz.kubalewski@intel.com>

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}'

  parent reply	other threads:[~2025-06-27 23:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-26 13:52 [PATCH net-next v7 0/3] dpll: add Reference SYNC feature Arkadiusz Kubalewski
2025-06-26 13:52 ` [PATCH net-next v7 1/3] dpll: add reference-sync netlink attribute Arkadiusz Kubalewski
2025-06-26 13:52 ` [PATCH net-next v7 2/3] dpll: add reference sync get/set Arkadiusz Kubalewski
2025-06-26 13:52 ` [PATCH net-next v7 3/3] ice: add ref-sync dpll pins Arkadiusz Kubalewski
2025-06-27 23:40 ` Jakub Kicinski [this message]
2025-06-27 23:50 ` [PATCH net-next v7 0/3] dpll: add Reference SYNC feature 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=20250627164035.3ef705fa@kernel.org \
    --to=kuba@kernel.org \
    --cc=aleksandr.loktionov@intel.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=anthony.l.nguyen@intel.com \
    --cc=arkadiusz.kubalewski@intel.com \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=donald.hunter@gmail.com \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jiri@resnulli.us \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=przemyslaw.kitszel@intel.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;
as well as URLs for NNTP newsgroup(s).