From: patchwork-bot+netdevbpf@kernel.org
To: Paolo Abeni <pabeni@redhat.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, dsahern@kernel.org,
edumazet@google.com, kuba@kernel.org, horms@kernel.org,
shuah@kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v2 net-next 0/2] ipv6: fix hangup on device removal
Date: Thu, 07 Nov 2024 02:00:33 +0000 [thread overview]
Message-ID: <173094483300.1489169.15053795359586095063.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1730828007.git.pabeni@redhat.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 5 Nov 2024 19:23:49 +0100 you wrote:
> This addresses the infamous unregister_netdevice splat in net selftests;
> the actual fix is carried by the first patch, while the 2nd one
> addresses a related problem in the relevant test that was patially
> hiding the problem.
>
> Targeting net-next as the issue is quite old and I feel a little lost
> in the fib info/nh jungle.
>
> [...]
Here is the summary with links:
- [v2,net-next,1/2] ipv6: release nexthop on device removal
https://git.kernel.org/netdev/net-next/c/eb02688c5c45
- [v2,net-next,2/2] selftests: net: really check for bg process completion
https://git.kernel.org/netdev/net-next/c/52ed077aa633
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:[~2024-11-07 2:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 18:23 [PATCH v2 net-next 0/2] ipv6: fix hangup on device removal Paolo Abeni
2024-11-05 18:23 ` [PATCH v2 net-next 1/2] ipv6: release nexthop " Paolo Abeni
2024-11-05 18:26 ` Eric Dumazet
2024-11-05 21:40 ` David Ahern
2024-11-06 9:11 ` Paolo Abeni
2024-11-05 18:23 ` [PATCH v2 net-next 2/2] selftests: net: really check for bg process completion Paolo Abeni
2024-11-05 21:40 ` David Ahern
2024-11-07 2: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=173094483300.1489169.15053795359586095063.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.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 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).