From: patchwork-bot+netdevbpf@kernel.org
To: Byungchul Park <byungchul@sk.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel_team@skhynix.com, harry.yoo@oracle.com, toke@redhat.com,
kuba@kernel.org, asml.silence@gmail.com, almasrymina@google.com,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
horms@kernel.org, ncardwell@google.com, kuniyu@google.com,
dsahern@kernel.org, sdf@fomichev.me, dw@davidwei.uk,
ap420073@gmail.com, dtatulea@nvidia.com, shivajikant@google.com
Subject: Re: [PATCH net-next v2] netmem, devmem, tcp: access pp fields through @desc in net_iov
Date: Fri, 28 Nov 2025 02:20:29 +0000 [thread overview]
Message-ID: <176429642952.114872.9731749260937365998.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251126043646.75869-1-byungchul@sk.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 26 Nov 2025 13:36:46 +0900 you wrote:
> Convert all the legacy code directly accessing the pp fields in net_iov
> to access them through @desc in net_iov.
>
> Signed-off-by: Byungchul Park <byungchul@sk.com>
> ---
> Changes from v1:
> 1. Drop 1/3 since it already has been worked in io-uring tree.
> 2. Drop 3/3 since it requires the io-uring change to be merged.
>
> [...]
Here is the summary with links:
- [net-next,v2] netmem, devmem, tcp: access pp fields through @desc in net_iov
https://git.kernel.org/netdev/net-next/c/df59bb5b9af3
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-28 2:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 4:36 Byungchul Park
2025-11-28 2:20 ` 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=176429642952.114872.9731749260937365998.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=almasrymina@google.com \
--cc=ap420073@gmail.com \
--cc=asml.silence@gmail.com \
--cc=byungchul@sk.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=dtatulea@nvidia.com \
--cc=dw@davidwei.uk \
--cc=edumazet@google.com \
--cc=harry.yoo@oracle.com \
--cc=horms@kernel.org \
--cc=kernel_team@skhynix.com \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=shivajikant@google.com \
--cc=toke@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
all inboxes | Powered by JetHome®