From: patchwork-bot+netdevbpf@kernel.org
To: Karl Mehltretter <kmehltretter@gmail.com>
Cc: hawk@kernel.org, ilias.apalodimas@linaro.org, kuba@kernel.org,
edumazet@google.com, pabeni@redhat.com, netdev@vger.kernel.org,
corbet@lwn.net, linux-doc@vger.kernel.org,
skhan@linuxfoundation.org, rdunlap@infradead.org,
aleksander.lobakin@intel.com
Subject: Re: [PATCH net-next] docs: networking: page_pool: Use page_pool_put_netmem_bulk() in the kernel-doc directive
Date: Thu, 10 Sep 2026 01:30:03 +0000 [thread overview]
Message-ID: <178900380388.1141351.12222446095741061422.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260905084711.40105-1-kmehltretter@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 5 Sep 2026 10:47:11 +0200 you wrote:
> page_pool.rst asks net/core/page_pool.c for page_pool_put_page_bulk().
> Commit 024bfd2e9d80 ("page_pool: make page_pool_put_page_bulk() handle
> array of netmems") renamed the function to page_pool_put_netmem_bulk().
> Since then the directive finds nothing and the bulk release helper is
> missing from the rendered page.
>
> Use the current name.
>
> [...]
Here is the summary with links:
- [net-next] docs: networking: page_pool: Use page_pool_put_netmem_bulk() in the kernel-doc directive
https://git.kernel.org/netdev/net-next/c/bcf03907c5ec
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-09-10 1:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-05 8:47 [PATCH net-next] docs: networking: page_pool: Use page_pool_put_netmem_bulk() in the kernel-doc directive Karl Mehltretter
2026-09-05 21:33 ` Randy Dunlap
2026-09-10 1: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=178900380388.1141351.12222446095741061422.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aleksander.lobakin@intel.com \
--cc=corbet@lwn.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=kmehltretter@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
/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.