From: patchwork-bot+netdevbpf@kernel.org
To: David Wei <dw@davidwei.uk>
Cc: netdev@vger.kernel.org, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, jdamato@fastly.com
Subject: Re: [PATCH net-next v1 0/2] io_uring/zcrx: selftests: more cleanups
Date: Tue, 29 Apr 2025 18:20:37 +0000 [thread overview]
Message-ID: <174595083798.1759531.8429412307722121984.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250426195525.1906774-1-dw@davidwei.uk>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 26 Apr 2025 12:55:23 -0700 you wrote:
> Patch 1 use rand_port() instead of hard coding port 9999. Patch 2 parses
> JSON from ethtool -g instead of string.
>
> David Wei (2):
> io_uring/zcrx: selftests: use rand_port
> io_uring/zcrx: selftests: parse json from ethtool -g
>
> [...]
Here is the summary with links:
- [net-next,v1,1/2] io_uring/zcrx: selftests: use rand_port()
https://git.kernel.org/netdev/net-next/c/187e0216366f
- [net-next,v1,2/2] io_uring/zcrx: selftests: parse json from ethtool -g
https://git.kernel.org/netdev/net-next/c/6fbb4d3f7262
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:[~2025-04-29 18:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-26 19:55 [PATCH net-next v1 0/2] io_uring/zcrx: selftests: more cleanups David Wei
2025-04-26 19:55 ` [PATCH net-next v1 1/2] io_uring/zcrx: selftests: use rand_port() David Wei
2025-04-28 17:11 ` Joe Damato
2025-04-26 19:55 ` [PATCH net-next v1 2/2] io_uring/zcrx: selftests: parse json from ethtool -g David Wei
2025-04-28 17:11 ` Joe Damato
2025-04-28 17:13 ` [PATCH net-next v1 0/2] io_uring/zcrx: selftests: more cleanups Joe Damato
2025-04-29 18: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=174595083798.1759531.8429412307722121984.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=jdamato@fastly.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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