From: patchwork-bot+netdevbpf@kernel.org
To: Xiao Liang <shaw.leon@gmail.com>
Cc: netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
kuniyu@amazon.com, kuba@kernel.org, davem@davemloft.net,
dsahern@kernel.org, edumazet@google.com, pabeni@redhat.com,
andrew+netdev@lunn.ch, horms@kernel.org, shuah@kernel.org,
donald.hunter@gmail.com, alex.aring@gmail.com,
stefan@datenfreihafen.org, miquel.raynal@bootlin.com,
steffen.klassert@secunet.com, herbert@gondor.apana.org.au,
linux-rdma@vger.kernel.org, linux-can@vger.kernel.org,
osmocom-net-gprs@lists.osmocom.org, bpf@vger.kernel.org,
linux-ppp@vger.kernel.org, wireguard@lists.zx2c4.com,
linux-wireless@vger.kernel.org, b.a.t.m.a.n@lists.open-mesh.org,
bridge@lists.linux.dev, linux-wpan@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v10 00/13] net: Improve netns handling in rtnetlink
Date: Fri, 21 Feb 2025 23:50:33 +0000 [thread overview]
Message-ID: <174018183327.2240430.4249639047640655494.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250219125039.18024-1-shaw.leon@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 19 Feb 2025 20:50:26 +0800 you wrote:
> This patch series includes some netns-related improvements and fixes for
> rtnetlink, to make link creation more intuitive:
>
> 1) Creating link in another net namespace doesn't conflict with link
> names in current one.
> 2) Refector rtnetlink link creation. Create link in target namespace
> directly.
>
> [...]
Here is the summary with links:
- [net-next,v10,01/13] rtnetlink: Lookup device in target netns when creating link
https://git.kernel.org/netdev/net-next/c/ec061546c6cf
- [net-next,v10,02/13] rtnetlink: Pack newlink() params into struct
https://git.kernel.org/netdev/net-next/c/69c7be1b903f
- [net-next,v10,03/13] net: Use link/peer netns in newlink() of rtnl_link_ops
https://git.kernel.org/netdev/net-next/c/cf517ac16ad9
- [net-next,v10,04/13] ieee802154: 6lowpan: Validate link netns in newlink() of rtnl_link_ops
https://git.kernel.org/netdev/net-next/c/3533717581dd
- [net-next,v10,05/13] net: ip_tunnel: Don't set tunnel->net in ip_tunnel_init()
https://git.kernel.org/netdev/net-next/c/9e17b2a1a097
- [net-next,v10,06/13] net: ip_tunnel: Use link netns in newlink() of rtnl_link_ops
https://git.kernel.org/netdev/net-next/c/eacb1160536e
- [net-next,v10,07/13] net: ipv6: Init tunnel link-netns before registering dev
https://git.kernel.org/netdev/net-next/c/db014522f356
- [net-next,v10,08/13] net: ipv6: Use link netns in newlink() of rtnl_link_ops
https://git.kernel.org/netdev/net-next/c/5e72ce3e3980
- [net-next,v10,09/13] net: xfrm: Use link netns in newlink() of rtnl_link_ops
https://git.kernel.org/netdev/net-next/c/5314e3d68455
- [net-next,v10,10/13] rtnetlink: Remove "net" from newlink params
https://git.kernel.org/netdev/net-next/c/9c0fc091dc01
- [net-next,v10,11/13] rtnetlink: Create link directly in target net namespace
https://git.kernel.org/netdev/net-next/c/7ca486d08a30
- [net-next,v10,12/13] selftests: net: Add python context manager for netns entering
https://git.kernel.org/netdev/net-next/c/030329416232
- [net-next,v10,13/13] selftests: net: Add test cases for link and peer netns
https://git.kernel.org/netdev/net-next/c/85cb3711acb8
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:[~2025-02-21 23:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 12:50 [PATCH net-next v10 00/13] net: Improve netns handling in rtnetlink Xiao Liang
2025-02-19 12:50 ` [PATCH net-next v10 01/13] rtnetlink: Lookup device in target netns when creating link Xiao Liang
2025-02-19 12:50 ` [PATCH net-next v10 02/13] rtnetlink: Pack newlink() params into struct Xiao Liang
2025-02-21 3:24 ` Kuniyuki Iwashima
2025-02-19 12:50 ` [PATCH net-next v10 03/13] net: Use link/peer netns in newlink() of rtnl_link_ops Xiao Liang
2025-02-19 12:50 ` [PATCH net-next v10 04/13] ieee802154: 6lowpan: Validate link " Xiao Liang
2025-02-19 12:50 ` [PATCH net-next v10 05/13] net: ip_tunnel: Don't set tunnel->net in ip_tunnel_init() Xiao Liang
2025-02-21 3:26 ` Kuniyuki Iwashima
2025-02-19 12:50 ` [PATCH net-next v10 06/13] net: ip_tunnel: Use link netns in newlink() of rtnl_link_ops Xiao Liang
2025-02-21 3:35 ` Kuniyuki Iwashima
2025-02-19 12:50 ` [PATCH net-next v10 07/13] net: ipv6: Init tunnel link-netns before registering dev Xiao Liang
2025-02-21 4:06 ` Kuniyuki Iwashima
2025-02-21 7:34 ` Xiao Liang
2025-02-19 12:50 ` [PATCH net-next v10 08/13] net: ipv6: Use link netns in newlink() of rtnl_link_ops Xiao Liang
2025-02-21 4:08 ` Kuniyuki Iwashima
2025-02-19 12:50 ` [PATCH net-next v10 09/13] net: xfrm: " Xiao Liang
2025-02-21 4:10 ` Kuniyuki Iwashima
2025-02-19 12:50 ` [PATCH net-next v10 10/13] rtnetlink: Remove "net" from newlink params Xiao Liang
2025-02-21 4:11 ` Kuniyuki Iwashima
2025-02-19 12:50 ` [PATCH net-next v10 11/13] rtnetlink: Create link directly in target net namespace Xiao Liang
2025-02-21 4:16 ` Kuniyuki Iwashima
2025-02-19 12:50 ` [PATCH net-next v10 12/13] selftests: net: Add python context manager for netns entering Xiao Liang
2025-02-19 12:50 ` [PATCH net-next v10 13/13] selftests: net: Add test cases for link and peer netns Xiao Liang
2025-02-21 23:47 ` [PATCH net-next v10 00/13] net: Improve netns handling in rtnetlink Jakub Kicinski
2025-02-21 23: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=174018183327.2240430.4249639047640655494.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alex.aring@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=bpf@vger.kernel.org \
--cc=bridge@lists.linux.dev \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-ppp@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linux-wpan@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=osmocom-net-gprs@lists.osmocom.org \
--cc=pabeni@redhat.com \
--cc=shaw.leon@gmail.com \
--cc=shuah@kernel.org \
--cc=stefan@datenfreihafen.org \
--cc=steffen.klassert@secunet.com \
--cc=wireguard@lists.zx2c4.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