From: patchwork-bot+netdevbpf@kernel.org
To: Hangbin Liu <liuhangbin@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
shuah@kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] selftests: net: use slowwait to make sure setup finished
Date: Thu, 19 Jun 2025 13:30:15 +0000 [thread overview]
Message-ID: <175033981599.865029.10714129256471908570.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250617105101.433718-1-liuhangbin@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 17 Jun 2025 10:50:58 +0000 you wrote:
> The two updated tests sometimes failed because the network setup hadn't
> completed. Used slowwait to ensure the setup finished and the tests
> always passed. I ran both tests 50 times, and all of them passed.
>
> Hangbin Liu (2):
> selftests: net: use slowwait to stabilize vrf_route_leaking test
> selftests: net: use slowwait to make sure IPv6 setup finished
>
> [...]
Here is the summary with links:
- [net-next,1/2] selftests: net: use slowwait to stabilize vrf_route_leaking test
https://git.kernel.org/netdev/net-next/c/d83a58067592
- [net-next,2/2] selftests: net: use slowwait to make sure IPv6 setup finished
https://git.kernel.org/netdev/net-next/c/948670361c0c
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-06-19 13:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 10:50 [PATCH net-next 0/2] selftests: net: use slowwait to make sure setup finished Hangbin Liu
2025-06-17 10:50 ` [PATCH net-next 1/2] selftests: net: use slowwait to stabilize vrf_route_leaking test Hangbin Liu
2025-06-18 10:33 ` Simon Horman
2025-06-17 10:51 ` [PATCH net-next 2/2] selftests: net: use slowwait to make sure IPv6 setup finished Hangbin Liu
2025-06-18 10:34 ` Simon Horman
2025-06-19 13: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=175033981599.865029.10714129256471908570.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--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 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.