From: patchwork-bot+netdevbpf@kernel.org
To: Anubhav Singh <anubhavsinggh@google.com>
Cc: netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, shuah@kernel.org,
willemb@google.com, lixiaoyan@google.com
Subject: Re: [PATCH net] selftests/net: use destination options instead of hop-by-hop
Date: Sat, 01 Nov 2025 00:40:10 +0000 [thread overview]
Message-ID: <176195761074.680160.2034732686013542470.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251030060436.1556664-1-anubhavsinggh@google.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 30 Oct 2025 06:04:36 +0000 you wrote:
> The GRO self-test, gro.c, currently constructs IPv6 packets containing a
> Hop-by-Hop Options header (IPPROTO_HOPOPTS) to ensure the GRO path
> correctly handles IPv6 extension headers.
>
> However, network elements may be configured to drop packets with the
> Hop-by-Hop Options header (HBH). This causes the self-test to fail
> in environments where such network elements are present.
>
> [...]
Here is the summary with links:
- [net] selftests/net: use destination options instead of hop-by-hop
https://git.kernel.org/netdev/net/c/f8e8486702ab
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:[~2025-11-01 0:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 6:04 [PATCH net] selftests/net: use destination options instead of hop-by-hop Anubhav Singh
2025-11-01 0: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=176195761074.680160.2034732686013542470.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=anubhavsinggh@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lixiaoyan@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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.