Re: [PATCH net-next v3 0/2] net: netmem: document design principles and intended direction

[patchwork-bot+netdevbpf]

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@xxxxxxxxxx>:

On Sat, 10 Oct 2026 03:36:07 +0000 you wrote:
> Because the networking stack and drivers are only partially converted to
> netmem_ref and current memory providers only supply unreadable net_iovs,
> automated code review and analysis tools (such as LLMs) frequently infer
> the wrong architectural invariants from existing code. Specifically,
> they often assume that page_pool's struct page APIs are primary rather
> than legacy wrappers, that memory providers always imply net_iov, that
> net_iov is inherently unreadable, or that callers should branch on or
> downcast netmem_ref directly.
> 
> [...]

Here is the summary with links:
  - [net-next,v3,1/2] net: netmem: document netmem and memory provider design in comments
    https://git.kernel.org/netdev/net-next/c/72ebc685bca9
  - [net-next,v3,2/2] docs: netmem: document netmem and memory provider design principles
    https://git.kernel.org/netdev/net-next/c/b35ec0d877f5

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html