From: patchwork-bot+netdevbpf@kernel.org
To: alex todadze <todadzealexi19@proton.me>
Cc: maxime.chevallier@bootlin.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
pabeni@redhat.com, mcoquelin.stm32@gmail.com,
alexandre.torgue@foss.st.com, netdev@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2] net: stmmac: fix rx checksum offload with extended descriptors
Date: Mon, 26 Oct 2026 23:30:07 +0000 [thread overview]
Message-ID: <179305740777.3456332.8291409987867601935.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261020-stmmac-rx-csum-v2-1-330c8d0951ea@proton.me>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 20 Oct 2026 22:42:24 +0000 you wrote:
> From: alex todadze <todadzealexi19@proton.me>
>
> With extended descriptors, bit 0 of RDES0 is the Extended Status
> Available flag. enh_desc_get_rx_status() still reads it as the payload
> checksum error bit of the checksum offload table, so every IP frame that
> has extended status is reported as csum_none and its checksum is
> verified again in software.
>
> [...]
Here is the summary with links:
- [net,v2] net: stmmac: fix rx checksum offload with extended descriptors
https://git.kernel.org/netdev/net/c/72ee27b97986
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-26 23:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 22:42 [PATCH net v2] net: stmmac: fix rx checksum offload with extended descriptors alex todadze via B4 Relay
2026-10-26 23:30 ` 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=179305740777.3456332.8291409987867601935.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@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=maxime.chevallier@bootlin.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=todadzealexi19@proton.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