From: Kory Maincent <kory.maincent@bootlin.com>
To: Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, Donald Hunter <donald.hunter@gmail.com>
Subject: Netlink specs, help dealing with nested array
Date: Fri, 21 Jun 2024 16:15:43 +0200 [thread overview]
Message-ID: <20240621161543.42617bef@kmaincent-XPS-13-7390> (raw)
Hello Jakub, Donald or other ynl experts,
I have an issue dealing with a nested array.
Here is my current netlink spec and ethtool patches:
https://termbin.com/gbyx
https://termbin.com/b325
Here is the error I got:
https://termbin.com/c7b1
I am trying to investigate what goes wrong with ynl but I still don't know.
If someone have an idea of what is going wrong with ynl or my specs it would be
lovely!
Regards,
--
Köry Maincent, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com
next reply other threads:[~2024-06-21 14:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 14:15 Kory Maincent [this message]
2024-06-21 15:14 ` Netlink specs, help dealing with nested array Donald Hunter
2024-06-21 15:19 ` Jakub Kicinski
2024-06-21 15:27 ` Donald Hunter
2024-06-21 15:56 ` Kory Maincent
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=20240621161543.42617bef@kmaincent-XPS-13-7390 \
--to=kory.maincent@bootlin.com \
--cc=donald.hunter@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
/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