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, ncardwell@google.com, kuniyu@amazon.com,
dsahern@kernel.org, willemb@google.com,
willemdebruijn.kernel@gmail.com, horms@kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH net v2] net-timestamp: support TCP GSO case for a few missing flags
Date: Wed, 05 Mar 2025 13:40:33 +0000 [thread overview]
Message-ID: <174118203351.886004.4860497203823639707.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250304004429.71477-1-kerneljasonxing@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Tue, 4 Mar 2025 08:44:29 +0800 you wrote:
> When I read through the TSO codes, I found out that we probably
> miss initializing the tx_flags of last seg when TSO is turned
> off, which means at the following points no more timestamp
> (for this last one) will be generated. There are three flags
> to be handled in this patch:
> 1. SKBTX_HW_TSTAMP
> 2. SKBTX_BPF
> 3. SKBTX_SCHED_TSTAMP
> Note that SKBTX_BPF[1] was added in 6.14.0-rc2 by commit
> 6b98ec7e882af ("bpf: Add BPF_SOCK_OPS_TSTAMP_SCHED_CB callback")
> and only belongs to net-next branch material for now. The common
> issue of the above three flags can be fixed by this single patch.
>
> [...]
Here is the summary with links:
- [net,v2] net-timestamp: support TCP GSO case for a few missing flags
https://git.kernel.org/netdev/net/c/3c9231ea6497
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-03-05 13:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 0:44 [PATCH net v2] net-timestamp: support TCP GSO case for a few missing flags Jason Xing
2025-03-04 14:01 ` Willem de Bruijn
2025-03-05 13:40 ` 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=174118203351.886004.4860497203823639707.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=kerneljasonxing@gmail.com \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).