From: patchwork-bot+netdevbpf@kernel.org
To: Wongi Lee <qw3rtyp0@gmail.com>
Cc: netdev@vger.kernel.org, dsahern@kernel.org, idosch@nvidia.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, asml.silence@gmail.com,
dhowells@redhat.com, willemb@google.com, jwlee2217@gmail.com
Subject: Re: [PATCH net v4 0/2] ipv4/ipv6: account for fraggap on paged allocation paths
Date: Sun, 21 Jun 2026 22:30:17 +0000 [thread overview]
Message-ID: <178208101700.524849.5372754030819859653.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <ajFQn6yh43eDeQm9@DESKTOP-19IMU7U.localdomain>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 16 Jun 2026 22:33:19 +0900 you wrote:
> Fix fraggap accounting in the paged-allocation paths of IPv4 and IPv6.
>
> The IPv6 patch is the v4 update of the previously posted patch. The IPv4
> patch handles the same code pattern (by Ido).
>
> v3->v4
> - Remove the MSG_SPLICE_PAGES exception from the IPv6 negative copy check.
> - Clarify where the fraggap bytes are copied in the commit messages.
> - Add Reviewed-by tags.
>
> [...]
Here is the summary with links:
- [net,v4,1/2] ipv4: account for fraggap on the paged allocation path
https://git.kernel.org/netdev/net/c/eca856950f7c
- [net,v4,2/2] ipv6: account for fraggap on the paged allocation path
https://git.kernel.org/netdev/net/c/736b380e28d0
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-06-21 22:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-16 13:33 [PATCH net v4 0/2] ipv4/ipv6: account for fraggap on paged allocation paths Wongi Lee
2026-06-16 13:38 ` [PATCH net v4 1/2] ipv4: account for fraggap on the paged allocation path Wongi Lee
2026-06-16 13:46 ` [PATCH net v4 2/2] ipv6: " Wongi Lee
2026-06-21 22: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=178208101700.524849.5372754030819859653.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=asml.silence@gmail.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=jwlee2217@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=qw3rtyp0@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox