From: patchwork-bot+netdevbpf@kernel.org
To: Maoyi Xie <maoyixie.tju@gmail.com>
Cc: kuba@kernel.org, davem@davemloft.net, pabeni@redhat.com,
edumazet@google.com, dsahern@kernel.org, kuniyu@google.com,
steffen.klassert@secunet.com, shaw.leon@gmail.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH net v4 0/2] ip6_vti: vti6_changelink and vti6_siocdevprivate netns fixes
Date: Tue, 26 May 2026 09:30:08 +0000 [thread overview]
Message-ID: <177978780814.3286183.4781727530904846983.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260521130555.3421684-1-maoyixie.tju@gmail.com>
Hello:
This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Thu, 21 May 2026 21:05:53 +0800 you wrote:
> v3 -> v4
>
> - Update Fixes tag on both patches to commit 61220ab34948
> ("vti6: Enable namespace changing"). Xiao noted the old tag
> 5e72ce3e3980 is not the introducing commit. dev_net(dev) and
> t->net first diverge when 61220ab34948 dropped
> NETIF_F_NETNS_LOCAL and made vti6 devices movable through
> IFLA_NET_NS_FD. Same Fixes shape Jakub took for the sibling
> fix 1d324c2f43f7.
>
> [...]
Here is the summary with links:
- [net,v4,1/2] ip6: vti: Use ip6_tnl.net in vti6_changelink().
https://git.kernel.org/netdev/net/c/11b326fb0a37
- [net,v4,2/2] ip6: vti: Use ip6_tnl.net in vti6_siocdevprivate().
https://git.kernel.org/netdev/net/c/8b484efd5cb4
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:[~2026-05-26 9:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 13:05 [PATCH net v4 0/2] ip6_vti: vti6_changelink and vti6_siocdevprivate netns fixes Maoyi Xie
2026-05-21 13:05 ` [PATCH net v4 1/2] ip6: vti: Use ip6_tnl.net in vti6_changelink() Maoyi Xie
2026-05-21 13:05 ` [PATCH net v4 2/2] ip6: vti: Use ip6_tnl.net in vti6_siocdevprivate() Maoyi Xie
2026-05-26 9:30 ` 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=177978780814.3286183.4781727530904846983.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maoyixie.tju@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shaw.leon@gmail.com \
--cc=stable@vger.kernel.org \
--cc=steffen.klassert@secunet.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