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, nicolas.dichtel@6wind.com, jiri@resnulli.us,
donald.hunter@gmail.com
Subject: Re: [PATCH net-next 0/8] tools: ynl-gen: fill in the gaps in support of legacy families
Date: Fri, 15 Dec 2023 02:01:18 +0000 [thread overview]
Message-ID: <170260567822.29932.4186848634489676352.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231213231432.2944749-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 13 Dec 2023 15:14:24 -0800 you wrote:
> Fill in the gaps in YNL C code gen so that we can generate user
> space code for all genetlink families for which we have specs.
>
> The two major changes we need are support for fixed headers and
> support for recursive nests.
>
> For fixed header support - place the struct for the fixed header
> directly in the request struct (and don't bother generating access
> helpers). The member of a fixed header can't be too complex, and
> also are by definition not optional so the user has to fill them in.
> The YNL core needs a bit of a tweak to understand that the attrs
> may now start at a fixed offset, which is not necessarily equal
> to sizeof(struct genlmsghdr).
>
> [...]
Here is the summary with links:
- [net-next,1/8] tools: ynl-gen: add missing request free helpers for dumps
https://git.kernel.org/netdev/net-next/c/4dc27587dcba
- [net-next,2/8] tools: ynl-gen: use enum user type for members and args
https://git.kernel.org/netdev/net-next/c/139c163b5b0b
- [net-next,3/8] tools: ynl-gen: support fixed headers in genetlink
https://git.kernel.org/netdev/net-next/c/f6805072c2aa
- [net-next,4/8] tools: ynl-gen: fill in implementations for TypeUnused
https://git.kernel.org/netdev/net-next/c/f967a498fce8
- [net-next,5/8] tools: ynl-gen: record information about recursive nests
https://git.kernel.org/netdev/net-next/c/38329fcfb757
- [net-next,6/8] tools: ynl-gen: re-sort ignoring recursive nests
https://git.kernel.org/netdev/net-next/c/aa75783b95a1
- [net-next,7/8] tools: ynl-gen: store recursive nests by a pointer
https://git.kernel.org/netdev/net-next/c/461f25a2e433
- [net-next,8/8] tools: ynl-gen: print prototypes for recursive stuff
https://git.kernel.org/netdev/net-next/c/7b5fe80ebc63
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-12-15 2:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 23:14 [PATCH net-next 0/8] tools: ynl-gen: fill in the gaps in support of legacy families Jakub Kicinski
2023-12-13 23:14 ` [PATCH net-next 1/8] tools: ynl-gen: add missing request free helpers for dumps Jakub Kicinski
2023-12-14 10:21 ` Donald Hunter
2023-12-13 23:14 ` [PATCH net-next 2/8] tools: ynl-gen: use enum user type for members and args Jakub Kicinski
2023-12-14 10:26 ` Donald Hunter
2023-12-13 23:14 ` [PATCH net-next 3/8] tools: ynl-gen: support fixed headers in genetlink Jakub Kicinski
2023-12-14 10:57 ` Donald Hunter
2023-12-13 23:14 ` [PATCH net-next 4/8] tools: ynl-gen: fill in implementations for TypeUnused Jakub Kicinski
2023-12-14 10:58 ` Donald Hunter
2023-12-13 23:14 ` [PATCH net-next 5/8] tools: ynl-gen: record information about recursive nests Jakub Kicinski
2023-12-14 11:02 ` Donald Hunter
2023-12-13 23:14 ` [PATCH net-next 6/8] tools: ynl-gen: re-sort ignoring " Jakub Kicinski
2023-12-14 11:12 ` Donald Hunter
2023-12-13 23:14 ` [PATCH net-next 7/8] tools: ynl-gen: store recursive nests by a pointer Jakub Kicinski
2023-12-14 11:11 ` Donald Hunter
2023-12-13 23:14 ` [PATCH net-next 8/8] tools: ynl-gen: print prototypes for recursive stuff Jakub Kicinski
2023-12-14 11:11 ` Donald Hunter
2023-12-15 2:01 ` 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=170260567822.29932.4186848634489676352.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=pabeni@redhat.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).