From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
donald.hunter@gmail.com, matttbe@kernel.org,
chuck.lever@oracle.com, daniel@iogearbox.net,
skhawaja@google.com, sdf@fomichev.me, hawk@kernel.org
Subject: Re: [PATCH net-next v3 1/2] net: page_pool: support dumping pps of a specific ifindex via Netlink
Date: Fri, 08 May 2026 22:00:22 +0000 [thread overview]
Message-ID: <177827762229.865600.2759908552685312593.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260506034821.1710113-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 5 May 2026 20:48:20 -0700 you wrote:
> NIPA tries to make sure that HW tests don't modify system state.
> It saves the state of page pools, too. Now that I write this commit
> message I realize that this is impractical since page pool IDs and
> state will get legitimately changed by the tests. But I already
> spent a couple of hours implementing the filtering, so..
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
>
> [...]
Here is the summary with links:
- [net-next,v3,1/2] net: page_pool: support dumping pps of a specific ifindex via Netlink
https://git.kernel.org/netdev/net-next/c/c93799de1bd2
- [net-next,v3,2/2] selftests: net: add tests for filtered dumps of page pool
https://git.kernel.org/netdev/net-next/c/ce3d4a67a076
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-05-08 22:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 3:48 [PATCH net-next v3 1/2] net: page_pool: support dumping pps of a specific ifindex via Netlink Jakub Kicinski
2026-05-06 3:48 ` [PATCH net-next v3 2/2] selftests: net: add tests for filtered dumps of page pool Jakub Kicinski
2026-05-08 22: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=177827762229.865600.2759908552685312593.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=chuck.lever@oracle.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=matttbe@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=skhawaja@google.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox