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, jacob.e.keller@intel.com, jiri@resnulli.us
Subject: Re: [PATCH net-next v2 00/15] devlink: code split and structured instance walk
Date: Fri, 06 Jan 2023 06:20:18 +0000 [thread overview]
Message-ID: <167298601834.4609.10563145944962909204.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230105040531.353563-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 4 Jan 2023 20:05:16 -0800 you wrote:
> Split devlink.c into a handful of files, trying to keep the "core"
> code away from all the command-specific implementations.
> The core code has been quite scattered until now. Going forward we can
> consider using a source file per-subobject, I think that it's quite
> beneficial to newcomers (based on relative ease with which folks
> contribute to ethtool vs devlink). But this series doesn't split
> everything out, yet - partially due to backporting concerns,
> but mostly due to lack of time. Bulk of the netlink command
> handling is left in a leftover.c file.
>
> [...]
Here is the summary with links:
- [net-next,v2,01/15] devlink: move code to a dedicated directory
(no matching commit)
- [net-next,v2,02/15] devlink: rename devlink_netdevice_event -> devlink_port_netdevice_event
https://git.kernel.org/netdev/net-next/c/e50ef40f9a9a
- [net-next,v2,03/15] devlink: split out core code
(no matching commit)
- [net-next,v2,04/15] devlink: split out netlink code
https://git.kernel.org/netdev/net-next/c/623cd13b1654
- [net-next,v2,05/15] netlink: add macro for checking dump ctx size
https://git.kernel.org/netdev/net-next/c/2c7bc10d0f7b
- [net-next,v2,06/15] devlink: use an explicit structure for dump context
https://git.kernel.org/netdev/net-next/c/3015f8224961
- [net-next,v2,07/15] devlink: remove start variables from dumps
https://git.kernel.org/netdev/net-next/c/20615659b514
- [net-next,v2,08/15] devlink: drop the filter argument from devlinks_xa_find_get
https://git.kernel.org/netdev/net-next/c/8861c0933c78
- [net-next,v2,09/15] devlink: health: combine loops in dump
https://git.kernel.org/netdev/net-next/c/a0e13dfdc391
- [net-next,v2,10/15] devlink: restart dump based on devlink instance ids (simple)
https://git.kernel.org/netdev/net-next/c/731d69a6bd13
- [net-next,v2,11/15] devlink: restart dump based on devlink instance ids (nested)
https://git.kernel.org/netdev/net-next/c/a8f947073f4a
- [net-next,v2,12/15] devlink: restart dump based on devlink instance ids (function)
https://git.kernel.org/netdev/net-next/c/c9666bac537e
- [net-next,v2,13/15] devlink: uniformly take the devlink instance lock in the dump loop
https://git.kernel.org/netdev/net-next/c/e4d5015bc11b
- [net-next,v2,14/15] devlink: add by-instance dump infra
https://git.kernel.org/netdev/net-next/c/07f3af66089e
- [net-next,v2,15/15] devlink: convert remaining dumps to the by-instance scheme
https://git.kernel.org/netdev/net-next/c/5ce76d78b996
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-06 6:21 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 4:05 [PATCH net-next v2 00/15] devlink: code split and structured instance walk Jakub Kicinski
2023-01-05 4:05 ` [PATCH net-next v2 01/15] devlink: move code to a dedicated directory Jakub Kicinski
2023-01-05 9:14 ` Jiri Pirko
2023-01-05 4:05 ` [PATCH net-next v2 02/15] devlink: rename devlink_netdevice_event -> devlink_port_netdevice_event Jakub Kicinski
2023-01-05 9:14 ` Jiri Pirko
2023-01-05 4:05 ` [PATCH net-next v2 03/15] devlink: split out core code Jakub Kicinski
2023-01-05 9:16 ` Jiri Pirko
2023-01-05 18:34 ` Jakub Kicinski
2023-01-06 0:13 ` Jacob Keller
2023-01-06 8:57 ` Jiri Pirko
2023-01-05 4:05 ` [PATCH net-next v2 04/15] devlink: split out netlink code Jakub Kicinski
2023-01-05 9:17 ` Jiri Pirko
2023-01-05 4:05 ` [PATCH net-next v2 05/15] netlink: add macro for checking dump ctx size Jakub Kicinski
2023-01-23 14:20 ` Ido Schimmel
2023-01-23 22:18 ` Jakub Kicinski
2023-01-05 4:05 ` [PATCH net-next v2 06/15] devlink: use an explicit structure for dump context Jakub Kicinski
2023-01-05 9:17 ` Jiri Pirko
2023-01-05 4:05 ` [PATCH net-next v2 07/15] devlink: remove start variables from dumps Jakub Kicinski
2023-01-05 9:18 ` Jiri Pirko
2023-01-05 4:05 ` [PATCH net-next v2 08/15] devlink: drop the filter argument from devlinks_xa_find_get Jakub Kicinski
2023-01-05 4:05 ` [PATCH net-next v2 09/15] devlink: health: combine loops in dump Jakub Kicinski
2023-01-05 4:05 ` [PATCH net-next v2 10/15] devlink: restart dump based on devlink instance ids (simple) Jakub Kicinski
2023-01-05 9:22 ` Jiri Pirko
2023-01-05 4:05 ` [PATCH net-next v2 11/15] devlink: restart dump based on devlink instance ids (nested) Jakub Kicinski
2023-01-05 4:05 ` [PATCH net-next v2 12/15] devlink: restart dump based on devlink instance ids (function) Jakub Kicinski
2023-01-05 4:05 ` [PATCH net-next v2 13/15] devlink: uniformly take the devlink instance lock in the dump loop Jakub Kicinski
2023-01-05 4:05 ` [PATCH net-next v2 14/15] devlink: add by-instance dump infra Jakub Kicinski
2023-01-05 9:24 ` Jiri Pirko
2023-01-06 0:16 ` Jacob Keller
2023-01-06 8:59 ` Jiri Pirko
2023-01-06 16:57 ` Jacob Keller
2023-01-05 4:05 ` [PATCH net-next v2 15/15] devlink: convert remaining dumps to the by-instance scheme Jakub Kicinski
2023-01-06 6:20 ` 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=167298601834.4609.10563145944962909204.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jacob.e.keller@intel.com \
--cc=jiri@resnulli.us \
--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).