From: Jakub Kicinski <kuba@kernel.org>
To: Paolo Abeni <pabeni@redhat.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Simon Horman <horms@kernel.org>,
Donald Hunter <donald.hunter@gmail.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Shuah Khan <shuah@kernel.org>,
Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Subject: Re: [PATCH net-next 00/10] geneve: introduce double tunnel GSO/GRO
Date: Wed, 26 Nov 2025 15:59:37 -0800 [thread overview]
Message-ID: <20251126155937.05a8c280@kernel.org> (raw)
In-Reply-To: <cover.1764056123.git.pabeni@redhat.com>
On Tue, 25 Nov 2025 17:11:05 +0100 Paolo Abeni wrote:
> This is the [belated] incarnation of topic discussed in the last Neconf
> [1].
You mentioned off-list that the ai-reported issues here are real, so:
pw-bot: cr
prev parent reply other threads:[~2025-11-26 23:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 16:11 [PATCH net-next 00/10] geneve: introduce double tunnel GSO/GRO Paolo Abeni
2025-11-25 16:11 ` [PATCH net-next 01/10] net: introduce mangleid_features Paolo Abeni
2025-11-25 16:11 ` [PATCH net-next 02/10] geneve: expose gso partial features for tunnel offload Paolo Abeni
2025-11-25 16:11 ` [PATCH net-next 03/10] vxlan: " Paolo Abeni
2025-11-25 16:11 ` [PATCH net-next 04/10] geneve: add netlink support for GRO hint Paolo Abeni
2025-11-25 16:11 ` [PATCH net-next 05/10] geneve: constify geneve_hlen() Paolo Abeni
2025-11-25 16:11 ` [PATCH net-next 06/10] geneve: pass the geneve device ptr to geneve_build_skb() Paolo Abeni
2025-11-25 16:11 ` [PATCH net-next 07/10] geneve: add GRO hint output path Paolo Abeni
2025-11-25 16:11 ` [PATCH net-next 08/10] geneve: extract hint option at GRO stage Paolo Abeni
2025-11-25 16:11 ` [PATCH net-next 09/10] geneve: use GRO hint option in the RX path Paolo Abeni
2025-11-25 16:11 ` [PATCH net-next 10/10] selftests: net: tests for add double tunneling GRO/GSO Paolo Abeni
2025-11-26 23:59 ` Jakub Kicinski [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=20251126155937.05a8c280@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=willemdebruijn.kernel@gmail.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.