From: patchwork-bot+netdevbpf@kernel.org
To: Carolina Jubran <cjubran@nvidia.com>
Cc: shuah@kernel.org, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
gal@nvidia.com, tariqt@nvidia.com, cratiu@nvidia.com,
noren@nvidia.com, mbloch@nvidia.com,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next V3 0/6] selftests: drv-net: Fix issues in devlink_rate_tc_bw.py
Date: Tue, 02 Dec 2025 01:20:30 +0000 [thread overview]
Message-ID: <176463843079.2624727.13926178837360430248.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251130091938.4109055-1-cjubran@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 30 Nov 2025 11:19:32 +0200 you wrote:
> Hi,
>
> This series fixes issues in the devlink_rate_tc_bw.py selftest and
> introduces a new Iperf3Runner that helps with measurement handling.
>
> Thanks,
> Carolina
>
> [...]
Here is the summary with links:
- [net-next,V3,1/6] selftests: drv-net: Add devlink_rate_tc_bw.py to TEST_PROGS
https://git.kernel.org/netdev/net-next/c/a8658f7bb650
- [net-next,V3,2/6] selftests: drv-net: introduce Iperf3Runner for measurement use cases
https://git.kernel.org/netdev/net-next/c/2a60ce94c6e8
- [net-next,V3,3/6] selftests: drv-net: Use Iperf3Runner in devlink_rate_tc_bw.py
https://git.kernel.org/netdev/net-next/c/cb1acbd30a42
- [net-next,V3,4/6] selftests: drv-net: Set shell=True for sysfs writes in devlink_rate_tc_bw.py
https://git.kernel.org/netdev/net-next/c/3796e549e305
- [net-next,V3,5/6] selftests: drv-net: Fix and clarify TC bandwidth split in devlink_rate_tc_bw.py
https://git.kernel.org/netdev/net-next/c/9ecd05a2c872
- [net-next,V3,6/6] selftests: drv-net: Fix tolerance calculation in devlink_rate_tc_bw.py
https://git.kernel.org/netdev/net-next/c/5cc1bddcfeb2
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-12-02 1:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-30 9:19 [PATCH net-next V3 0/6] selftests: drv-net: Fix issues in devlink_rate_tc_bw.py Carolina Jubran
2025-11-30 9:19 ` [PATCH net-next V3 1/6] selftests: drv-net: Add devlink_rate_tc_bw.py to TEST_PROGS Carolina Jubran
2025-11-30 9:19 ` [PATCH net-next V3 2/6] selftests: drv-net: introduce Iperf3Runner for measurement use cases Carolina Jubran
2025-11-30 9:19 ` [PATCH net-next V3 3/6] selftests: drv-net: Use Iperf3Runner in devlink_rate_tc_bw.py Carolina Jubran
2025-11-30 9:19 ` [PATCH net-next V3 4/6] selftests: drv-net: Set shell=True for sysfs writes " Carolina Jubran
2025-11-30 9:19 ` [PATCH net-next V3 5/6] selftests: drv-net: Fix and clarify TC bandwidth split " Carolina Jubran
2025-11-30 9:19 ` [PATCH net-next V3 6/6] selftests: drv-net: Fix tolerance calculation " Carolina Jubran
2025-12-02 1: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=176463843079.2624727.13926178837360430248.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=cjubran@nvidia.com \
--cc=cratiu@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=noren@nvidia.com \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=tariqt@nvidia.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