From: patchwork-bot+netdevbpf@kernel.org
To: Stanislav Fomichev <sdf@fomichev.me>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, horms@kernel.org,
donald.hunter@gmail.com, corbet@lwn.net, andrew+netdev@lunn.ch,
kory.maincent@bootlin.com, nicolas.dichtel@6wind.com
Subject: Re: [PATCH net-next v4 0/8] ethtool: generate uapi header from the spec
Date: Thu, 05 Dec 2024 20:50:32 +0000 [thread overview]
Message-ID: <173343183250.2063743.5447149013565962028.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241204155549.641348-1-sdf@fomichev.me>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 4 Dec 2024 07:55:41 -0800 you wrote:
> We keep expanding ethtool netlink api surface and this leads to
> constantly playing catchup on the ynl spec side. There are a couple
> of things that prevent us from fully converting to generating
> the header from the spec (stats and cable tests), but we can
> generate 95% of the header which is still better than maintaining
> c header and spec separately. The series adds a couple of missing
> features on the ynl-gen-c side and separates the parts
> that we can generate into new ethtool_netlink_generated.h.
>
> [...]
Here is the summary with links:
- [net-next,v4,1/8] ynl: support enum-cnt-name attribute in legacy definitions
https://git.kernel.org/netdev/net-next/c/523d3cc4b6d1
- [net-next,v4,2/8] ynl: skip rendering attributes with header property in uapi mode
https://git.kernel.org/netdev/net-next/c/8c843ecde4e4
- [net-next,v4,3/8] ynl: support directional specs in ynl-gen-c.py
https://git.kernel.org/netdev/net-next/c/56881d07f0b4
- [net-next,v4,4/8] ynl: add missing pieces to ethtool spec to better match uapi header
https://git.kernel.org/netdev/net-next/c/0187e602c03c
- [net-next,v4,5/8] ynl: include uapi header after all dependencies
https://git.kernel.org/netdev/net-next/c/001b0b59efbb
- [net-next,v4,6/8] ethtool: separate definitions that are gonna be generated
https://git.kernel.org/netdev/net-next/c/49922401c219
- [net-next,v4,7/8] ethtool: remove the comments that are not gonna be generated
https://git.kernel.org/netdev/net-next/c/dd7cde36de15
- [net-next,v4,8/8] ethtool: regenerate uapi header from the spec
https://git.kernel.org/netdev/net-next/c/8d0580c6ebdd
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:[~2024-12-05 20:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 15:55 [PATCH net-next v4 0/8] ethtool: generate uapi header from the spec Stanislav Fomichev
2024-12-04 15:55 ` [PATCH net-next v4 1/8] ynl: support enum-cnt-name attribute in legacy definitions Stanislav Fomichev
2024-12-04 15:55 ` [PATCH net-next v4 2/8] ynl: skip rendering attributes with header property in uapi mode Stanislav Fomichev
2024-12-04 15:55 ` [PATCH net-next v4 3/8] ynl: support directional specs in ynl-gen-c.py Stanislav Fomichev
2024-12-04 15:55 ` [PATCH net-next v4 4/8] ynl: add missing pieces to ethtool spec to better match uapi header Stanislav Fomichev
2024-12-04 15:55 ` [PATCH net-next v4 5/8] ynl: include uapi header after all dependencies Stanislav Fomichev
2024-12-04 15:55 ` [PATCH net-next v4 6/8] ethtool: separate definitions that are gonna be generated Stanislav Fomichev
2024-12-04 15:55 ` [PATCH net-next v4 7/8] ethtool: remove the comments that are not " Stanislav Fomichev
2024-12-04 15:55 ` [PATCH net-next v4 8/8] ethtool: regenerate uapi header from the spec Stanislav Fomichev
2024-12-05 20:50 ` 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=173343183250.2063743.5447149013565962028.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
/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