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
Subject: Re: [PATCH net-next 00/10] tools: ynl-gen: dust off the user space code
Date: Sat, 03 Jun 2023 06:30:24 +0000 [thread overview]
Message-ID: <168577382467.1168.8506596151079358044.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230602023548.463441-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 1 Jun 2023 19:35:38 -0700 you wrote:
> Every now and then I wish I finished the user space part of
> the netlink specs, Python scripts kind of stole the show but
> C is useful for selftests and stuff which needs to be fast.
> Recently someone asked me how to access devlink and ethtool
> from C++ which pushed me over the edge.
>
> Fix things which bit rotted and finish notification handling.
> This series contains code gen changes only. I'll follow up
> with the fixed component, samples and docs as soon as it's
> merged.
>
> [...]
Here is the summary with links:
- [net-next,01/10] tools: ynl-gen: add extra headers for user space
https://git.kernel.org/netdev/net-next/c/91dfaef243cd
- [net-next,02/10] tools: ynl-gen: fix unused / pad attribute handling
https://git.kernel.org/netdev/net-next/c/6ad49839ba9b
- [net-next,03/10] tools: ynl-gen: don't override pure nested struct
https://git.kernel.org/netdev/net-next/c/67c65ce762ad
- [net-next,04/10] tools: ynl-gen: loosen type consistency check for events
https://git.kernel.org/netdev/net-next/c/5605f102378f
- [net-next,05/10] tools: ynl-gen: add error checking for nested structs
https://git.kernel.org/netdev/net-next/c/eef9b794eac8
- [net-next,06/10] tools: ynl-gen: generate enum-to-string helpers
https://git.kernel.org/netdev/net-next/c/21b6e302789c
- [net-next,07/10] tools: ynl-gen: move the response reading logic into YNL
https://git.kernel.org/netdev/net-next/c/dc0956c98f11
- [net-next,08/10] tools: ynl-gen: generate alloc and free helpers for req
https://git.kernel.org/netdev/net-next/c/5d58f911c755
- [net-next,09/10] tools: ynl-gen: switch to family struct
https://git.kernel.org/netdev/net-next/c/8cb6afb33541
- [net-next,10/10] tools: ynl-gen: generate static descriptions of notifications
https://git.kernel.org/netdev/net-next/c/59d814f0f285
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-06-03 6:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 2:35 [PATCH net-next 00/10] tools: ynl-gen: dust off the user space code Jakub Kicinski
2023-06-02 2:35 ` [PATCH net-next 01/10] tools: ynl-gen: add extra headers for user space Jakub Kicinski
2023-06-02 2:35 ` [PATCH net-next 02/10] tools: ynl-gen: fix unused / pad attribute handling Jakub Kicinski
2023-06-02 2:35 ` [PATCH net-next 03/10] tools: ynl-gen: don't override pure nested struct Jakub Kicinski
2023-06-02 2:35 ` [PATCH net-next 04/10] tools: ynl-gen: loosen type consistency check for events Jakub Kicinski
2023-06-02 2:35 ` [PATCH net-next 05/10] tools: ynl-gen: add error checking for nested structs Jakub Kicinski
2023-06-02 2:35 ` [PATCH net-next 06/10] tools: ynl-gen: generate enum-to-string helpers Jakub Kicinski
2023-06-02 2:35 ` [PATCH net-next 07/10] tools: ynl-gen: move the response reading logic into YNL Jakub Kicinski
2023-06-02 2:35 ` [PATCH net-next 08/10] tools: ynl-gen: generate alloc and free helpers for req Jakub Kicinski
2023-06-02 2:35 ` [PATCH net-next 09/10] tools: ynl-gen: switch to family struct Jakub Kicinski
2023-06-02 2:35 ` [PATCH net-next 10/10] tools: ynl-gen: generate static descriptions of notifications Jakub Kicinski
2023-06-03 6:30 ` 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=168577382467.1168.8506596151079358044.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--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).