From: patchwork-bot+netdevbpf@kernel.org
To: Gal Pressman <gal@nvidia.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, andrew+netdev@lunn.ch, netdev@vger.kernel.org,
horms@kernel.org, shuah@kernel.org, leitao@debian.org,
dw@davidwei.uk, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next v3 0/2] selftests: net: fix cmd.process() timeout handling
Date: Thu, 12 Mar 2026 02:20:29 +0000 [thread overview]
Message-ID: <177328202904.3908053.2650272713884965081.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260310115803.2521050-1-gal@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 10 Mar 2026 13:58:01 +0200 you wrote:
> Pass the timeout argument correctly in cmd.process().
> As Jakub noted, fixing the timeout broke the bpftrace() command in
> netpoll_basic.py, so fix it first.
>
> Changelog:
> v2->v3: https://lore.kernel.org/all/20260308192126.2490631-1-gal@nvidia.com/
> * Resubmit to net-next.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/2] selftests: net: pass bpftrace timeout to cmd()
https://git.kernel.org/netdev/net-next/c/82562972b854
- [net-next,v3,2/2] selftests: net: fix timeout passed as positional argument to communicate()
https://git.kernel.org/netdev/net-next/c/f0bd19316663
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-03-12 2:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 11:58 [PATCH net-next v3 0/2] selftests: net: fix cmd.process() timeout handling Gal Pressman
2026-03-10 11:58 ` [PATCH net-next v3 1/2] selftests: net: pass bpftrace timeout to cmd() Gal Pressman
2026-03-10 11:58 ` [PATCH net-next v3 2/2] selftests: net: fix timeout passed as positional argument to communicate() Gal Pressman
2026-03-12 2:20 ` 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=177328202904.3908053.2650272713884965081.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dw@davidwei.uk \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=leitao@debian.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox