From: patchwork-bot+netdevbpf@kernel.org
To: Marc Harvey <marcharvey@google.com>
Cc: jiri@resnulli.us, andrew+netdev@lunn.ch, edumazet@google.com,
willemb@google.com, maheshb@google.com, netdev@vger.kernel.org,
linux-kselftest@vger.kernel.org, kuba@kernel.org,
liuhangbin@gmail.com
Subject: Re: [PATCH net-next v3] selftests: net: Add tests to verify team driver option set and get.
Date: Thu, 11 Sep 2025 09:10:07 +0000 [thread overview]
Message-ID: <175758180751.2096638.16103651833506796423.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250905040441.2679296-1-marcharvey@google.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 5 Sep 2025 04:04:41 +0000 you wrote:
> There are currently no kernel tests that verify setting and getting
> options of the team driver.
>
> In the future, options may be added that implicitly change other
> options, which will make it useful to have tests like these that show
> nothing breaks. There will be a follow up patch to this that adds new
> "rx_enabled" and "tx_enabled" options, which will implicitly affect the
> "enabled" option value and vice versa.
>
> [...]
Here is the summary with links:
- [net-next,v3] selftests: net: Add tests to verify team driver option set and get.
https://git.kernel.org/netdev/net-next/c/db1b60066686
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-09-11 9:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 4:04 [PATCH net-next v3] selftests: net: Add tests to verify team driver option set and get Marc Harvey
2025-09-11 9:10 ` 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=175758180751.2096638.16103651833506796423.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=edumazet@google.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--cc=maheshb@google.com \
--cc=marcharvey@google.com \
--cc=netdev@vger.kernel.org \
--cc=willemb@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