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, robh@kernel.org, johannes@sipsolutions.net,
stephen@networkplumber.org, ecree.xilinx@gmail.com,
sdf@google.com, f.fainelli@gmail.com, fw@strlen.de,
linux-doc@vger.kernel.org, razor@blackwall.org,
nicolas.dichtel@6wind.com
Subject: Re: [PATCH net-next v4 0/8] Netlink protocol specs
Date: Tue, 24 Jan 2023 10:40:18 +0000 [thread overview]
Message-ID: <167455681853.26386.14381375194899546381.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230120175041.342573-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 20 Jan 2023 09:50:33 -0800 you wrote:
> I think the Netlink proto specs are far along enough to merge.
> Filling in all attribute types and quirks will be an ongoing
> effort but we have enough to cover FOU so it's somewhat complete.
>
> I fully intend to continue polishing the code but at the same
> time I'd like to start helping others base their work on the
> specs (e.g. DPLL) and need to start working on some new families
> myself.
>
> [...]
Here is the summary with links:
- [net-next,v4,1/8] docs: add more netlink docs (incl. spec docs)
https://git.kernel.org/netdev/net-next/c/9d6a65079c98
- [net-next,v4,2/8] netlink: add schemas for YAML specs
https://git.kernel.org/netdev/net-next/c/e616c07ca518
- [net-next,v4,3/8] net: add basic C code generators for Netlink
https://git.kernel.org/netdev/net-next/c/be5bea1cc0bf
- [net-next,v4,4/8] netlink: add a proto specification for FOU
https://git.kernel.org/netdev/net-next/c/4eb77b4ecd3c
- [net-next,v4,5/8] net: fou: regenerate the uAPI from the spec
https://git.kernel.org/netdev/net-next/c/3a330496baa8
- [net-next,v4,6/8] net: fou: rename the source for linking
https://git.kernel.org/netdev/net-next/c/08d323234d10
- [net-next,v4,7/8] net: fou: use policy and operation tables generated from the spec
https://git.kernel.org/netdev/net-next/c/1d562c32e439
- [net-next,v4,8/8] tools: ynl: add a completely generic client
https://git.kernel.org/netdev/net-next/c/e4b48ed460d3
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-01-24 10:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 17:50 [PATCH net-next v4 0/8] Netlink protocol specs Jakub Kicinski
2023-01-20 17:50 ` [PATCH net-next v4 1/8] docs: add more netlink docs (incl. spec docs) Jakub Kicinski
2023-01-20 17:50 ` [PATCH net-next v4 2/8] netlink: add schemas for YAML specs Jakub Kicinski
2023-01-20 17:50 ` [PATCH net-next v4 3/8] net: add basic C code generators for Netlink Jakub Kicinski
2023-01-20 17:50 ` [PATCH net-next v4 4/8] netlink: add a proto specification for FOU Jakub Kicinski
2023-01-20 17:50 ` [PATCH net-next v4 5/8] net: fou: regenerate the uAPI from the spec Jakub Kicinski
2023-01-24 17:49 ` Alexander Lobakin
2023-01-24 18:50 ` Johannes Berg
2023-01-25 0:40 ` Jakub Kicinski
2023-01-25 10:16 ` Alexander Lobakin
2023-01-20 17:50 ` [PATCH net-next v4 6/8] net: fou: rename the source for linking Jakub Kicinski
2023-01-20 17:50 ` [PATCH net-next v4 7/8] net: fou: use policy and operation tables generated from the spec Jakub Kicinski
2023-01-20 17:50 ` [PATCH net-next v4 8/8] tools: ynl: add a completely generic client Jakub Kicinski
2023-01-24 10:29 ` [PATCH net-next v4 0/8] Netlink protocol specs Paolo Abeni
2023-01-24 10: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=167455681853.26386.14381375194899546381.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=fw@strlen.de \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=robh@kernel.org \
--cc=sdf@google.com \
--cc=stephen@networkplumber.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;
as well as URLs for NNTP newsgroup(s).