From: patchwork-bot+netdevbpf@kernel.org
To: Jisheng Zhang <jszhang@kernel.org>
Cc: maxime.chevallier@bootlin.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, mcoquelin.stm32@gmail.com,
alexandre.torgue@foss.st.com, netdev@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: stmmac: Disable unsolicited checksum insertion for AF_XDP TX
Date: Mon, 05 Oct 2026 22:50:05 +0000 [thread overview]
Message-ID: <179124060528.1926729.1824950688409199711.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260929121032.20835-1-jszhang@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 29 Sep 2026 20:10:32 +0800 you wrote:
> stmmac enables TX checksum insertion for every AF_XDP packet on queues
> that support it. The driver does not implement tmo_request_checksum(), so
> it enables the offload regardless of whether the application requested it
> and ignores the requested checksum offsets.
>
> Disable checksum insertion in the AF_XDP TX path. Applications must supply
> complete checksums until the driver can honor AF_XDP checksum metadata.
>
> [...]
Here is the summary with links:
- net: stmmac: Disable unsolicited checksum insertion for AF_XDP TX
https://git.kernel.org/netdev/net-next/c/ecf5985006dd
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-10-05 22:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 12:10 [PATCH] net: stmmac: Disable unsolicited checksum insertion for AF_XDP TX Jisheng Zhang
2026-09-29 12:34 ` netdev-bot+sinfo
2026-10-05 22:50 ` 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=179124060528.1926729.1824950688409199711.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jszhang@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=mcoquelin.stm32@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 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.