From: patchwork-bot+netdevbpf@kernel.org
To: Coco Li <lixiaoyan@google.com>
Cc: davem@davemloft.net, yoshfuji@linux-ipv6.org, dsahern@kernel.org,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
michael.chan@broadcom.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v6 1/2] IPv6/GRO: generic helper to remove temporary HBH/jumbo header in driver
Date: Tue, 13 Dec 2022 00:00:17 +0000 [thread overview]
Message-ID: <167088961714.16932.15471195808501226642.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221210041646.3587757-1-lixiaoyan@google.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 10 Dec 2022 04:16:45 +0000 you wrote:
> IPv6/TCP and GRO stacks can build big TCP packets with an added
> temporary Hop By Hop header.
>
> Is GSO is not involved, then the temporary header needs to be removed in
> the driver. This patch provides a generic helper for drivers that need
> to modify their headers in place.
>
> [...]
Here is the summary with links:
- [net-next,v6,1/2] IPv6/GRO: generic helper to remove temporary HBH/jumbo header in driver
https://git.kernel.org/netdev/net-next/c/89300468e2b2
- [RFC,net-next,v6,2/2] bnxt: Use generic HBH removal helper in tx path
https://git.kernel.org/netdev/net-next/c/b6488b161ab2
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:[~2022-12-13 0:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-10 4:16 [PATCH net-next v6 1/2] IPv6/GRO: generic helper to remove temporary HBH/jumbo header in driver Coco Li
2022-12-10 4:16 ` [RFC net-next v6 2/2] bnxt: Use generic HBH removal helper in tx path Coco Li
2022-12-11 5:07 ` Michael Chan
2022-12-13 0:00 ` 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=167088961714.16932.15471195808501226642.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lixiaoyan@google.com \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yoshfuji@linux-ipv6.org \
/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