From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Zahka <daniel.zahka@gmail.com>
Cc: alexanderduyck@fb.com, kuba@kernel.org, kernel-team@meta.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
pabeni@redhat.com, dimitri.daskalakis1@gmail.com,
mohsin.bashr@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/6] eth: mpnic: checksum and segmentation offloads
Date: Fri, 13 Nov 2026 16:40:07 +0000 [thread overview]
Message-ID: <179458800703.1155704.6123486269782874455.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261110-mpnic-lso-v2-0-ccd37b051d08@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 10 Nov 2026 14:06:33 -0800 you wrote:
> Add checksum and segmentation offload support. Tx checksum offload
> follows the generic csum_start/csum_offset model. Rx checksum also
> follows the normal unnecessary/complete model. The device can validate l4
> checksums for tcp or udp, when the l3 type is one of: ipv4, ipv6,
> ipv4-in-ipv6, or ipv6-in-ipv6. The full l2 checksum of a frame is always
> passed to driver via a Rx completion descriptor field, which can be used
> for checksum complete on other packet types.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/6] eth: mpnic: Tx checksum offload
https://git.kernel.org/netdev/net-next/c/164fe254d1e8
- [net-next,v2,2/6] eth: mpnic: Rx checksum offload
https://git.kernel.org/netdev/net-next/c/47fcc7451a71
- [net-next,v2,3/6] eth: mpnic: TCP segmentation offload
https://git.kernel.org/netdev/net-next/c/148df1a778fc
- [net-next,v2,4/6] eth: mpnic: UDP segmentation offload
https://git.kernel.org/netdev/net-next/c/6617d7ba6ea8
- [net-next,v2,5/6] eth: mpnic: IPv4 and IPv6 in IPv6 tunnel segmentation
https://git.kernel.org/netdev/net-next/c/25284507aca0
- [net-next,v2,6/6] eth: mpnic: add GSO_PARTIAL for other tunnels
https://git.kernel.org/netdev/net-next/c/0ad78e7740d4
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-11-13 16:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 22:06 Daniel Zahka
2026-11-10 22:06 ` [PATCH net-next v2 1/6] eth: mpnic: Tx checksum offload Daniel Zahka
2026-11-12 10:08 ` netdev-bot+sashiko
2026-11-10 22:06 ` [PATCH net-next v2 2/6] eth: mpnic: Rx " Daniel Zahka
2026-11-10 22:06 ` [PATCH net-next v2 3/6] eth: mpnic: TCP segmentation offload Daniel Zahka
2026-11-12 10:08 ` netdev-bot+sashiko
2026-11-12 11:49 ` Daniel Zahka
2026-11-10 22:06 ` [PATCH net-next v2 4/6] eth: mpnic: UDP " Daniel Zahka
2026-11-12 10:08 ` netdev-bot+sashiko
2026-11-12 11:03 ` Daniel Zahka
2026-11-10 22:06 ` [PATCH net-next v2 5/6] eth: mpnic: IPv4 and IPv6 in IPv6 tunnel segmentation Daniel Zahka
2026-11-12 10:08 ` netdev-bot+sashiko
2026-11-12 12:49 ` Daniel Zahka
2026-11-10 22:06 ` [PATCH net-next v2 6/6] eth: mpnic: add GSO_PARTIAL for other tunnels Daniel Zahka
2026-11-13 16: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=179458800703.1155704.6123486269782874455.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexanderduyck@fb.com \
--cc=andrew+netdev@lunn.ch \
--cc=daniel.zahka@gmail.com \
--cc=davem@davemloft.net \
--cc=dimitri.daskalakis1@gmail.com \
--cc=edumazet@kernel.org \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mohsin.bashr@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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
all inboxes | Powered by JetHome®