From: patchwork-bot+netdevbpf@kernel.org
To: Hamza Mahfooz <hamzamahfooz@linux.microsoft.com>
Cc: netdev@vger.kernel.org, haiyangz@microsoft.com,
wei.liu@kernel.org, decui@microsoft.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, stephen@networkplumber.org,
linux-hyperv@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net] net: mana: report RX checksum offload for IPv6
Date: Thu, 12 Nov 2026 17:10:04 +0000 [thread overview]
Message-ID: <179450340453.540799.10106995147021439469.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261109142856.779955-1-hamzamahfooz@linux.microsoft.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 9 Nov 2026 09:28:56 -0500 you wrote:
> The hardware validates TCP and UDP checksums for both IPv4 and IPv6 and
> reports the result in rx_tcp_csum_succeed and rx_udp_csum_succeed.
> However, mana_rx_skb() also requires rx_iphdr_csum_succeed before it
> sets CHECKSUM_UNNECESSARY. That bit is only set for IPv4 (since IPv6
> has no header checksum), so IPv6 TCP and UDP traffic is always
> checksummed again in software.
>
> [...]
Here is the summary with links:
- [net] net: mana: report RX checksum offload for IPv6
https://git.kernel.org/netdev/net/c/bbcd02741c4c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-11-12 17:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 14:28 [PATCH net] net: mana: report RX checksum offload for IPv6 Hamza Mahfooz
2026-11-10 14:29 ` sashiko-bot
2026-11-10 15:41 ` Hamza Mahfooz
2026-11-12 17:10 ` patchwork-bot+netdevbpf [this message]
2026-11-13 2:31 ` netdev-bot+sashiko
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=179450340453.540799.10106995147021439469.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=edumazet@kernel.org \
--cc=haiyangz@microsoft.com \
--cc=hamzamahfooz@linux.microsoft.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=wei.liu@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.