All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Dragos Tatulea <dtatulea@nvidia.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, horms@kernel.org, donald.hunter@gmail.com,
	andrew+netdev@lunn.ch, asml.silence@gmail.com, axboe@kernel.dk,
	shuah@kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, io-uring@vger.kernel.org,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/2] netdev: expose page pool order via netlink
Date: Mon, 15 Jun 2026 20:30:08 +0000	[thread overview]
Message-ID: <178155540839.284807.2185512260142204749.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260612211709.1456966-2-dtatulea@nvidia.com>

Hello:

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

On Sat, 13 Jun 2026 00:17:02 +0300 you wrote:
> This small series exposes io_uring's high order page configuration
> via the page_pool netlink interface and updates the appropriate
> selftest to check this value.
> 
> ---
> v2:
> - Switched from exposing page_pool order to rx_buf_len via nl_fill of
>   the io_uring memory provider.
> - Updated selftest to check rx_buf_len.
> - v1: https://lore.kernel.org/all/20260611161235.3807332-1-dtatulea@nvidia.com/
> 
> [...]

Here is the summary with links:
  - [net-next,v2,1/2] netdev: expose io_uring rx_page_order order via netlink
    https://git.kernel.org/netdev/net-next/c/5c4adb7fb46f
  - [net-next,v2,2/2] io_uring/zcrx: selftests: verify rx_buf_len for large chunks
    https://git.kernel.org/netdev/net-next/c/18f65355e112

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



      parent reply	other threads:[~2026-06-15 20:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-12 21:17 [PATCH net-next v2 0/2] netdev: expose page pool order via netlink Dragos Tatulea
2026-06-12 21:17 ` [PATCH net-next v2 1/2] netdev: expose io_uring rx_page_order " Dragos Tatulea
2026-06-13  9:53   ` Pavel Begunkov
2026-06-13 14:09     ` Dragos Tatulea
2026-06-14  0:02       ` Jakub Kicinski
2026-06-15 11:16         ` Pavel Begunkov
2026-06-15 20:00           ` Jakub Kicinski
2026-06-15 10:53       ` Pavel Begunkov
2026-06-12 21:17 ` [PATCH net-next v2 2/2] io_uring/zcrx: selftests: verify rx_buf_len for large chunks Dragos Tatulea
2026-06-15 20: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=178155540839.284807.2185512260142204749.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=davem@davemloft.net \
    --cc=donald.hunter@gmail.com \
    --cc=dtatulea@nvidia.com \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=io-uring@vger.kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shuah@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.