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, andrew+netdev@lunn.ch, horms@kernel.org,
donald.hunter@gmail.com, ast@kernel.org, daniel@iogearbox.net,
hawk@kernel.org, john.fastabend@gmail.com, sdf@fomichev.me,
razor@blackwall.org, dw@davidwei.uk, bpf@vger.kernel.org
Subject: Re: [PATCH net-next] netlink: specs: netdev: update doc for xsk tx-checksum and zc-max-segs
Date: Fri, 18 Sep 2026 00:00:08 +0000 [thread overview]
Message-ID: <178968960837.187564.13298642054405181183.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260916021608.1702731-1-kuba@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 15 Sep 2026 19:16:08 -0700 you wrote:
> Minor touch ups to the XSK-related doc strings in the netdev spec.
>
> Tx checksum is (obviously?) Layer 4 (TCP/UDP), not Layer 3 (IP).
>
> The xdp_zc_max_segs change is more subtle, I guess, but to kernel devs
> saying "frags" may sound like the number of skb frags. The value includes
> the head in this case. The default of 1 means single buffer, XDP_USE_SG
> sockets are refused when it is 1. Let's use the word "buffer" instead
> of "frag".
>
> [...]
Here is the summary with links:
- [net-next] netlink: specs: netdev: update doc for xsk tx-checksum and zc-max-segs
https://git.kernel.org/netdev/net-next/c/8050e0efd4cf
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:[~2026-09-18 0:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 2:16 [PATCH net-next] netlink: specs: netdev: update doc for xsk tx-checksum and zc-max-segs Jakub Kicinski
2026-09-18 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=178968960837.187564.13298642054405181183.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=dw@davidwei.uk \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=horms@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=sdf@fomichev.me \
/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