From: patchwork-bot+netdevbpf@kernel.org
To: Paolo Abeni <pabeni@redhat.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, horms@kernel.org, shuah@kernel.org,
willemb@google.com, richardbgobert@gmail.com,
linux-kselftest@vger.kernel.org, aleksander.lobakin@intel.com
Subject: Re: [PATCH v2 net 0/2] net: gro: fix outer network offset
Date: Wed, 04 Feb 2026 03:30:09 +0000 [thread overview]
Message-ID: <177017580987.2166000.3434486648244735239.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1770032084.git.pabeni@redhat.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 2 Feb 2026 12:43:13 +0100 you wrote:
> The GRO stage has still problems in some edge scenarios when dealing
> with encapsulated traffic: the first patch address an issue there
> leading to bad checksums.
>
> The second patch introduces a test case covering the relevant scenario:
> S/W segmentation after GRO for encapsulated traffic.
>
> [...]
Here is the summary with links:
- [v2,net,1/2] net: gro: fix outer network offset
https://git.kernel.org/netdev/net/c/5c2c3c38be39
- [v2,net,2/2] selftest: net: add a test-case for encap segmentation after GRO
https://git.kernel.org/netdev/net/c/bee60ce21b75
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-02-04 3:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 11:43 [PATCH v2 net 0/2] net: gro: fix outer network offset Paolo Abeni
2026-02-02 11:43 ` [PATCH v2 net 1/2] " Paolo Abeni
2026-02-02 12:22 ` Eric Dumazet
2026-02-02 11:43 ` [PATCH v2 net 2/2] selftest: net: add a test-case for encap segmentation after GRO Paolo Abeni
2026-02-04 3: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=177017580987.2166000.3434486648244735239.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aleksander.lobakin@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardbgobert@gmail.com \
--cc=shuah@kernel.org \
--cc=willemb@google.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.