From: patchwork-bot+netdevbpf@kernel.org
To: Sverdlin@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org,
Alexander <alexander.sverdlin@siemens.com>
Cc: netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, shuah@kernel.org,
vladimir.oltean@nxp.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v3] selftests: net: local_termination: Wait for interfaces to come up
Date: Sat, 08 Nov 2025 02:50:06 +0000 [thread overview]
Message-ID: <176257020625.1230661.9266574979799210382.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251106161213.459501-1-alexander.sverdlin@siemens.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 6 Nov 2025 17:12:09 +0100 you wrote:
> From: Alexander Sverdlin <alexander.sverdlin@siemens.com>
>
> It seems that most of the tests prepare the interfaces once before the test
> run (setup_prepare()), rely on setup_wait() to wait for link and only then
> run the test(s).
>
> local_termination brings the physical interfaces down and up during test
> run but never wait for them to come up. If the auto-negotiation takes
> some seconds, first test packets are being lost, which leads to
> false-negative test results.
>
> [...]
Here is the summary with links:
- [net,v3] selftests: net: local_termination: Wait for interfaces to come up
https://git.kernel.org/netdev/net/c/57531b341644
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-11-08 2:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 16:12 [PATCH net v3] selftests: net: local_termination: Wait for interfaces to come up A. Sverdlin
2025-11-08 2: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=176257020625.1230661.9266574979799210382.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Sverdlin@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=alexander.sverdlin@siemens.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=vladimir.oltean@nxp.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