From: patchwork-bot+netdevbpf@kernel.org
To: Jason Xing <kerneljasonxing@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, shuah@kernel.org,
willemdebruijn.kernel@gmail.com, willemb@google.com,
linux-kselftest@vger.kernel.org, netdev@vger.kernel.org,
kernelxing@tencent.com
Subject: Re: [PATCH net-next v2] selftests: return failure when timestamps can't be reported
Date: Tue, 10 Sep 2024 00:00:34 +0000 [thread overview]
Message-ID: <172592643426.3961170.381877473938074234.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240905160035.62407-1-kerneljasonxing@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 6 Sep 2024 00:00:35 +0800 you wrote:
> From: Jason Xing <kernelxing@tencent.com>
>
> When I was trying to modify the tx timestamping feature, I found that
> running "./txtimestamp -4 -C -L 127.0.0.1" didn't reflect the error:
> I succeeded to generate timestamp stored in the skb but later failed
> to report it to the userspace (which means failed to put css into cmsg).
> It can happen when someone writes buggy codes in __sock_recv_timestamp(),
> for example.
>
> [...]
Here is the summary with links:
- [net-next,v2] selftests: return failure when timestamps can't be reported
https://git.kernel.org/netdev/net-next/c/a7e387375f22
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-09-10 0:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 16:00 [PATCH net-next v2] selftests: return failure when timestamps can't be reported Jason Xing
2024-09-09 17:23 ` Jakub Kicinski
2024-09-09 17:38 ` Willem de Bruijn
2024-09-10 0: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=172592643426.3961170.381877473938074234.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kerneljasonxing@gmail.com \
--cc=kernelxing@tencent.com \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=willemb@google.com \
--cc=willemdebruijn.kernel@gmail.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