All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Ratheesh Kannoth <rkannoth@marvell.com>
Cc: Netdev <netdev@vger.kernel.org>
Subject: Re: ynl newbie question
Date: Fri, 24 Oct 2025 08:09:59 -0700	[thread overview]
Message-ID: <20251024080959.55e7679d@kernel.org> (raw)
In-Reply-To: <MN0PR18MB5847A875201DF2889543A61DD3F1A@MN0PR18MB5847.namprd18.prod.outlook.com>

On Fri, 24 Oct 2025 13:39:57 +0000 Ratheesh Kannoth wrote:
> HI List,
> 
> Followed.
> https://docs.kernel.org/userspace-api/netlink/intro-specs.html
> 
> But I get following error.
> 
> root@rkannoth-OptiPlex-7090:~/linux# ./tools/net/ynl/pyynl/cli.py --spec Documentation/netlink/specs/ethtool.yaml       --do rings-get       --json '{"header":{"dev-index": 18}}'
>   File "./tools/net/ynl/pyynl/cli.py", line 19
>     schema_dir = os.path.abspath(f"{script_dir}/{relative_schema_dir}")
>                                                                      ^
> 
> Should I install anything ? there is no "/usr/share/ynl" directory
> (code cloned  from  https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)

I think you trimmed the stack trace a little too much?

But my guess if you're having issues with the schema is Python support
for jsonschema.

BTW if you're using Fedora ynl is part of kernel-tools.
Not sure if it propagated to RHEL/CentOS yet.

       reply	other threads:[~2025-10-24 15:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <MN0PR18MB5847A875201DF2889543A61DD3F1A@MN0PR18MB5847.namprd18.prod.outlook.com>
2025-10-24 15:09 ` Jakub Kicinski [this message]
2025-10-25 13:10   ` Re: ynl newbie question Ratheesh Kannoth
2025-10-27 10:31     ` Donald Hunter
2025-10-27 15:04       ` [EXTERNAL] " Ratheesh Kannoth

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=20251024080959.55e7679d@kernel.org \
    --to=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rkannoth@marvell.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.