From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, sdf@google.com, linux-doc@vger.kernel.org
Subject: Re: [PATCH net-next v2 00/14] tools: ynl: more docs and basic ethtool support
Date: Wed, 01 Feb 2023 04:40:19 +0000 [thread overview]
Message-ID: <167522641938.28256.15256621461698900503.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230131023354.1732677-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 30 Jan 2023 18:33:40 -0800 you wrote:
> I got discouraged from supporting ethtool in specs, because
> generating the user space C code seems a little tricky.
> The messages are ID'ed in a "directional" way (to and from
> kernel are separate ID "spaces"). There is value, however,
> in having the spec and being able to for example use it
> in Python.
>
> [...]
Here is the summary with links:
- [net-next,v2,01/14] tools: ynl-gen: prevent do / dump reordering
https://git.kernel.org/netdev/net-next/c/eaf317e7d2bb
- [net-next,v2,02/14] tools: ynl: move the cli and netlink code around
https://git.kernel.org/netdev/net-next/c/4e4480e89c47
- [net-next,v2,03/14] tools: ynl: add an object hierarchy to represent parsed spec
https://git.kernel.org/netdev/net-next/c/3aacf8281336
- [net-next,v2,04/14] tools: ynl: use the common YAML loading and validation code
https://git.kernel.org/netdev/net-next/c/30a5c6c8104f
- [net-next,v2,05/14] tools: ynl: add support for types needed by ethtool
https://git.kernel.org/netdev/net-next/c/19b64b48a33e
- [net-next,v2,06/14] tools: ynl: support directional enum-model in CLI
https://git.kernel.org/netdev/net-next/c/fd0616d34274
- [net-next,v2,07/14] tools: ynl: support multi-attr
https://git.kernel.org/netdev/net-next/c/90256f3f8093
- [net-next,v2,08/14] tools: ynl: support pretty printing bad attribute names
https://git.kernel.org/netdev/net-next/c/4cd2796f3f8d
- [net-next,v2,09/14] tools: ynl: use operation names from spec on the CLI
https://git.kernel.org/netdev/net-next/c/8dfec0a88868
- [net-next,v2,10/14] tools: ynl: load jsonschema on demand
https://git.kernel.org/netdev/net-next/c/5c6674f6eb52
- [net-next,v2,11/14] netlink: specs: finish up operation enum-models
https://git.kernel.org/netdev/net-next/c/8403bf044530
- [net-next,v2,12/14] netlink: specs: add partial specification for ethtool
https://git.kernel.org/netdev/net-next/c/b784db7ae840
- [net-next,v2,13/14] docs: netlink: add a starting guide for working with specs
https://git.kernel.org/netdev/net-next/c/01e47a372268
- [net-next,v2,14/14] tools: net: use python3 explicitly
https://git.kernel.org/netdev/net-next/c/981cbcb030d9
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-02-01 4:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 2:33 [PATCH net-next v2 00/14] tools: ynl: more docs and basic ethtool support Jakub Kicinski
2023-01-31 2:33 ` [PATCH net-next v2 01/14] tools: ynl-gen: prevent do / dump reordering Jakub Kicinski
2023-01-31 2:33 ` [PATCH net-next v2 02/14] tools: ynl: move the cli and netlink code around Jakub Kicinski
2023-01-31 2:33 ` [PATCH net-next v2 03/14] tools: ynl: add an object hierarchy to represent parsed spec Jakub Kicinski
2023-01-31 2:33 ` [PATCH net-next v2 04/14] tools: ynl: use the common YAML loading and validation code Jakub Kicinski
2023-01-31 2:33 ` [PATCH net-next v2 05/14] tools: ynl: add support for types needed by ethtool Jakub Kicinski
2023-01-31 2:33 ` [PATCH net-next v2 06/14] tools: ynl: support directional enum-model in CLI Jakub Kicinski
2023-01-31 2:33 ` [PATCH net-next v2 07/14] tools: ynl: support multi-attr Jakub Kicinski
2023-01-31 2:33 ` [PATCH net-next v2 08/14] tools: ynl: support pretty printing bad attribute names Jakub Kicinski
2023-01-31 2:33 ` [PATCH net-next v2 09/14] tools: ynl: use operation names from spec on the CLI Jakub Kicinski
2023-01-31 2:33 ` [PATCH net-next v2 10/14] tools: ynl: load jsonschema on demand Jakub Kicinski
2023-01-31 2:33 ` [PATCH net-next v2 11/14] netlink: specs: finish up operation enum-models Jakub Kicinski
2023-01-31 2:33 ` [PATCH net-next v2 12/14] netlink: specs: add partial specification for ethtool Jakub Kicinski
2023-01-31 2:33 ` [PATCH net-next v2 13/14] docs: netlink: add a starting guide for working with specs Jakub Kicinski
2023-01-31 2:33 ` [PATCH net-next v2 14/14] tools: net: use python3 explicitly Jakub Kicinski
2023-02-01 4:40 ` patchwork-bot+netdevbpf [this message]
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=167522641938.28256.15256621461698900503.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@google.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 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).