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, sd@queasysnail.net, leon@kernel.org
Subject: Re: [PATCH net-next v2 0/2] net: store netdevs in an xarray
Date: Fri, 28 Jul 2023 19:00:23 +0000 [thread overview]
Message-ID: <169057082308.523.12097779537419544794.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230726185530.2247698-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 26 Jul 2023 11:55:28 -0700 you wrote:
> One of more annoying developer experience gaps we have in netlink
> is iterating over netdevs. It's painful. Add an xarray to make
> it trivial.
>
> v2:
> - fix the potential mishandling of wrapping (Leon)
> v1: https://lore.kernel.org/all/20230722014237.4078962-1-kuba@kernel.org/
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] net: store netdevs in an xarray
https://git.kernel.org/netdev/net-next/c/759ab1edb56c
- [net-next,v2,2/2] net: convert some netlink netdev iterators to depend on the xarray
https://git.kernel.org/netdev/net-next/c/84e00d9bd4e4
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-07-28 19:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 18:55 [PATCH net-next v2 0/2] net: store netdevs in an xarray Jakub Kicinski
2023-07-26 18:55 ` [PATCH net-next v2 1/2] " Jakub Kicinski
2023-07-27 13:08 ` Leon Romanovsky
2023-07-27 15:45 ` Jakub Kicinski
2023-07-28 4:53 ` Leon Romanovsky
2023-07-28 15:27 ` Jakub Kicinski
2023-07-28 23:23 ` Stephen Hemminger
2023-07-29 0:07 ` Jakub Kicinski
2023-07-26 18:55 ` [PATCH net-next v2 2/2] net: convert some netlink netdev iterators to depend on the xarray Jakub Kicinski
2023-07-27 13:10 ` Leon Romanovsky
2023-07-28 19:00 ` 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=169057082308.523.12097779537419544794.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sd@queasysnail.net \
/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.