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, jiri@resnulli.us, johannes@sipsolutions.net
Subject: Re: [PATCH net-next v3 00/10] genetlink: provide struct genl_info to dumps
Date: Tue, 15 Aug 2023 22:10:24 +0000 [thread overview]
Message-ID: <169213742475.30940.13714880161407370687.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230814214723.2924989-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 14 Aug 2023 14:47:13 -0700 you wrote:
> One of the biggest (which is not to say only) annoyances with genetlink
> handling today is that doit and dumpit need some of the same information,
> but it is passed to them in completely different structs.
>
> The implementations commonly end up writing a _fill() method which
> populates a message and have to pass at least 6 parameters. 3 of which
> are extracted manually from request info.
>
> [...]
Here is the summary with links:
- [net-next,v3,01/10] genetlink: push conditional locking into dumpit/done
https://git.kernel.org/netdev/net-next/c/84817d8c6042
- [net-next,v3,02/10] genetlink: make genl_info->nlhdr const
https://git.kernel.org/netdev/net-next/c/fde9bd4a4d41
- [net-next,v3,03/10] genetlink: remove userhdr from struct genl_info
https://git.kernel.org/netdev/net-next/c/bffcc6882a1b
- [net-next,v3,04/10] genetlink: add struct genl_info to struct genl_dumpit_info
https://git.kernel.org/netdev/net-next/c/9272af109fe6
- [net-next,v3,05/10] genetlink: use attrs from struct genl_info
https://git.kernel.org/netdev/net-next/c/7288dd2fd488
- [net-next,v3,06/10] genetlink: add a family pointer to struct genl_info
https://git.kernel.org/netdev/net-next/c/5c670a010de4
- [net-next,v3,07/10] genetlink: add genlmsg_iput() API
https://git.kernel.org/netdev/net-next/c/5aa51d9f889c
- [net-next,v3,08/10] netdev-genl: use struct genl_info for reply construction
https://git.kernel.org/netdev/net-next/c/0e19d3108aea
- [net-next,v3,09/10] ethtool: netlink: simplify arguments to ethnl_default_parse()
https://git.kernel.org/netdev/net-next/c/ec0e5b09b834
- [net-next,v3,10/10] ethtool: netlink: always pass genl_info to .prepare_data
https://git.kernel.org/netdev/net-next/c/f946270d05c2
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-08-15 22:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 21:47 [PATCH net-next v3 00/10] genetlink: provide struct genl_info to dumps Jakub Kicinski
2023-08-14 21:47 ` [PATCH net-next v3 01/10] genetlink: push conditional locking into dumpit/done Jakub Kicinski
2023-08-14 21:47 ` [PATCH net-next v3 02/10] genetlink: make genl_info->nlhdr const Jakub Kicinski
2023-08-14 21:47 ` [PATCH net-next v3 03/10] genetlink: remove userhdr from struct genl_info Jakub Kicinski
2023-08-14 21:47 ` [Drbd-dev] " Jakub Kicinski
2023-08-15 12:49 ` [ovs-dev] " Aaron Conole
2023-08-15 12:49 ` [Drbd-dev] " Aaron Conole
2023-08-14 21:47 ` [PATCH net-next v3 04/10] genetlink: add struct genl_info to struct genl_dumpit_info Jakub Kicinski
2023-08-14 21:47 ` [PATCH net-next v3 05/10] genetlink: use attrs from struct genl_info Jakub Kicinski
2023-08-15 21:46 ` kernel test robot
2023-08-14 21:47 ` [PATCH net-next v3 06/10] genetlink: add a family pointer to " Jakub Kicinski
2023-08-14 21:47 ` [PATCH net-next v3 07/10] genetlink: add genlmsg_iput() API Jakub Kicinski
2023-08-14 21:47 ` [PATCH net-next v3 08/10] netdev-genl: use struct genl_info for reply construction Jakub Kicinski
2023-08-14 21:47 ` [PATCH net-next v3 09/10] ethtool: netlink: simplify arguments to ethnl_default_parse() Jakub Kicinski
2023-08-14 21:47 ` [PATCH net-next v3 10/10] ethtool: netlink: always pass genl_info to .prepare_data Jakub Kicinski
2023-08-15 6:06 ` Jiri Pirko
2023-08-15 22:10 ` 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=169213742475.30940.13714880161407370687.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jiri@resnulli.us \
--cc=johannes@sipsolutions.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.