From: patchwork-bot+netdevbpf@kernel.org
To: Bui Quang Minh <minhquangbui99@gmail.com>
Cc: netdev@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
davem@davemloft.net, kuba@kernel.org, hawk@kernel.org,
john.fastabend@gmail.com, edumazet@google.com, pabeni@redhat.com,
horms@kernel.org, maciej.fijalkowski@intel.com,
aleksander.lobakin@intel.com, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/2] xsk: respect the offsets when copying frags
Date: Tue, 29 Apr 2025 21:40:31 +0000 [thread overview]
Message-ID: <174596283150.1804413.6332242799239007270.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250426081220.40689-1-minhquangbui99@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 26 Apr 2025 15:12:18 +0700 you wrote:
> Hi everyone,
>
> In commit 560d958c6c68 ("xsk: add generic XSk &xdp_buff -> skb
> conversion"), we introduce a helper to convert zerocopy xdp_buff to skb.
> However, in the frag copy, we mistakenly ignore the frag's offset. This
> series adds the missing offset when copying frags in
> xdp_copy_frags_from_zc(). This function is not used anywhere so no
> backport is needed.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] xsk: respect the offsets when copying frags
https://git.kernel.org/netdev/net-next/c/ebaebc5eaf43
- [net-next,v2,2/2] xsk: convert xdp_copy_frags_from_zc() to use page_pool_dev_alloc()
https://git.kernel.org/netdev/net-next/c/7ead4405e06f
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-04-29 21:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-26 8:12 [PATCH net-next v2 0/2] xsk: respect the offsets when copying frags Bui Quang Minh
2025-04-26 8:12 ` [PATCH net-next v2 1/2] " Bui Quang Minh
2025-04-26 8:12 ` [PATCH net-next v2 2/2] xsk: convert xdp_copy_frags_from_zc() to use page_pool_dev_alloc() Bui Quang Minh
2025-04-29 21: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=174596283150.1804413.6332242799239007270.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aleksander.lobakin@intel.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=horms@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=minhquangbui99@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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