From: patchwork-bot+netdevbpf@kernel.org
To: Alexander Duyck <alexander.duyck@gmail.com>
Cc: netdev@vger.kernel.org, hawk@kernel.org,
ilias.apalodimas@linaro.org, davem@davemloft.net,
kuba@kernel.org, alexanderduyck@fb.com
Subject: Re: [net-next PATCH v3] page_pool: Refactor page_pool to enable fragmenting after allocation
Date: Thu, 03 Feb 2022 12:10:09 +0000 [thread overview]
Message-ID: <164389020903.26884.1681096827552466800.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <164364711160.2192.13812169156456875778.stgit@localhost.localdomain>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Mon, 31 Jan 2022 08:40:01 -0800 you wrote:
> From: Alexander Duyck <alexanderduyck@fb.com>
>
> This change is meant to permit a driver to perform "fragmenting" of the
> page from within the driver instead of the current model which requires
> pre-partitioning the page. The main motivation behind this is to support
> use cases where the page will be split up by the driver after DMA instead
> of before.
>
> [...]
Here is the summary with links:
- [net-next,v3] page_pool: Refactor page_pool to enable fragmenting after allocation
https://git.kernel.org/netdev/net-next/c/52cc6ffc0ab2
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:[~2022-02-03 12:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 16:40 [net-next PATCH v3] page_pool: Refactor page_pool to enable fragmenting after allocation Alexander Duyck
2022-02-03 12:10 ` 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=164389020903.26884.1681096827552466800.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexander.duyck@gmail.com \
--cc=alexanderduyck@fb.com \
--cc=davem@davemloft.net \
--cc=hawk@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.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.