From: patchwork-bot+netdevbpf@kernel.org
To: Stanislav Fomichev <sdf.kernel@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, edumazet@kernel.org,
horms@kernel.org, sdf@fomichev.me, bobbyeshleman@meta.com,
almasrymina@google.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: devmem: remove net_iov_area base_virtual
Date: Wed, 07 Oct 2026 02:00:11 +0000 [thread overview]
Message-ID: <179133841127.2870283.3925575192538703161.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261005201822.3060658-1-sdf@fomichev.me>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 5 Oct 2026 13:18:22 -0700 you wrote:
> Since commit 083e64a3af77 ("net: devmem: replace gen_pool with
> freelist"), a binding has a single net_iov_area covering the whole
> dma-buf, and base_virtual is always 0. Its only reader is
> net_iov_virtual_addr(), where it adds nothing. io_uring zcrx never
> uses it.
>
> Drop the field and the store, and compute the dma-buf offset from the
> net_iov index alone.
>
> [...]
Here is the summary with links:
- [net-next] net: devmem: remove net_iov_area base_virtual
https://git.kernel.org/netdev/net-next/c/7d3e5984d0fc
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-10-07 2:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 20:18 [PATCH net-next] net: devmem: remove net_iov_area base_virtual Stanislav Fomichev
2026-10-06 7:10 ` Mina Almasry
2026-10-07 2: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=179133841127.2870283.3925575192538703161.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=almasrymina@google.com \
--cc=bobbyeshleman@meta.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf.kernel@gmail.com \
--cc=sdf@fomichev.me \
/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.