From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, shuah@kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next 1/2] selftests: net: fix timestamp not arriving in cmsg_time.sh
Date: Sat, 11 May 2024 01:30:29 +0000 [thread overview]
Message-ID: <171539102997.31003.15681328963726859289.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240510005705.43069-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 9 May 2024 17:57:04 -0700 you wrote:
> On slow machines the SND timestamp sometimes doesn't arrive before
> we quit. The test only waits as long as the packet delay, so it's
> easy for a race condition to happen.
>
> Double the wait but do a bit of polling, once the SND timestamp
> arrives there's no point to wait any longer.
>
> [...]
Here is the summary with links:
- [net-next,1/2] selftests: net: fix timestamp not arriving in cmsg_time.sh
https://git.kernel.org/netdev/net-next/c/2d3b8dfd82d7
- [net-next,2/2] selftests: net: increase the delay for relative cmsg_time.sh test
https://git.kernel.org/netdev/net-next/c/b9d5f5711dd8
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-05-11 1:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 0:57 [PATCH net-next 1/2] selftests: net: fix timestamp not arriving in cmsg_time.sh Jakub Kicinski
2024-05-10 0:57 ` [PATCH net-next 2/2] selftests: net: increase the delay for relative cmsg_time.sh test Jakub Kicinski
2024-05-10 2:25 ` Willem de Bruijn
2024-05-10 2:49 ` [PATCH net-next 1/2] selftests: net: fix timestamp not arriving in cmsg_time.sh Willem de Bruijn
2024-05-11 1:23 ` Jakub Kicinski
2024-05-11 1: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=171539102997.31003.15681328963726859289.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--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 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.