From: patchwork-bot+netdevbpf@kernel.org
To: Fernando Fernandez Mancera <fmancera@suse.de>
Cc: netdev@vger.kernel.org, nicolas.dichtel@6wind.com,
stephen@networkplumber.org, horms@kernel.org, pabeni@redhat.com,
kuba@kernel.org, edumazet@google.com, davem@davemloft.net,
idosch@nvidia.com, dsahern@kernel.org
Subject: Re: [PATCH net v3 0/6] ipv6: fix error handling in disable_ipv6 sysctl
Date: Wed, 24 Jun 2026 02:20:49 +0000 [thread overview]
Message-ID: <178226764994.2513445.6893091614764518724.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260622130857.5115-1-fmancera@suse.de>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 22 Jun 2026 15:08:51 +0200 you wrote:
> While working on a different IPv6 patch series I have spotted multiple
> minor bugs around sysctl error handling and notifications. In general,
> they are not serious issues.
>
> In addition, there is one more issue in forwarding sysctl as it does not
> check for CAP_NET_ADMIN for the namespace. I am keeping that patch out
> of this series and I am aiming it at the net-next tree once it re-opens.
>
> [...]
Here is the summary with links:
- [net,v3,1/6] ipv6: fix error handling in disable_ipv6 sysctl
https://git.kernel.org/netdev/net/c/c779441e5070
- [net,v3,2/6] ipv6: fix error handling in ignore_routes_with_linkdown sysctl
https://git.kernel.org/netdev/net/c/cf4f2b14401f
- [net,v3,3/6] ipv6: fix error handling in forwarding sysctl
https://git.kernel.org/netdev/net/c/058b9b19f963
- [net,v3,4/6] ipv6: fix error handling in disable_policy sysctl
https://git.kernel.org/netdev/net/c/3e0e51c0ee1d
- [net,v3,5/6] ipv6: fix state corruption during proxy_ndp sysctl restart
https://git.kernel.org/netdev/net/c/6a1b50e585f0
- [net,v3,6/6] ipv6: fix missing notification for ignore_routes_with_linkdown
https://git.kernel.org/netdev/net/c/17dc3b245de4
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-06-24 2:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 13:08 [PATCH net v3 0/6] ipv6: fix error handling in disable_ipv6 sysctl Fernando Fernandez Mancera
2026-06-22 13:08 ` [PATCH net v3 1/6] " Fernando Fernandez Mancera
2026-06-22 13:08 ` [PATCH net v3 2/6] ipv6: fix error handling in ignore_routes_with_linkdown sysctl Fernando Fernandez Mancera
2026-06-22 13:08 ` [PATCH net v3 3/6] ipv6: fix error handling in forwarding sysctl Fernando Fernandez Mancera
2026-06-22 13:08 ` [PATCH net v3 4/6] ipv6: fix error handling in disable_policy sysctl Fernando Fernandez Mancera
2026-06-22 13:08 ` [PATCH net v3 5/6] ipv6: fix state corruption during proxy_ndp sysctl restart Fernando Fernandez Mancera
2026-06-22 13:08 ` [PATCH net v3 6/6] ipv6: fix missing notification for ignore_routes_with_linkdown Fernando Fernandez Mancera
2026-06-22 15:35 ` [PATCH net v3 0/6] ipv6: fix error handling in disable_ipv6 sysctl Ido Schimmel
2026-06-24 2: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=178226764994.2513445.6893091614764518724.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=fmancera@suse.de \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=pabeni@redhat.com \
--cc=stephen@networkplumber.org \
/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.