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,
shuah@kernel.org, willemb@google.com, petrm@nvidia.com,
sdf@fomichev.me, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next 1/2] selftests: drv-net: factor out a DrvEnv base class
Date: Tue, 11 Feb 2025 03:30:44 +0000 [thread overview]
Message-ID: <173924464474.3948401.15014700951334326245.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250207184140.1730466-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 7 Feb 2025 10:41:39 -0800 you wrote:
> We have separate Env classes for local tests and tests with a remote
> endpoint. Make it easier to share the code by creating a base class.
> Make env loading a method of this class.
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> .../selftests/drivers/net/lib/py/env.py | 59 +++++++++++--------
> 1 file changed, 33 insertions(+), 26 deletions(-)
Here is the summary with links:
- [net-next,1/2] selftests: drv-net: factor out a DrvEnv base class
https://git.kernel.org/netdev/net-next/c/29604bc2aaed
- [net-next,2/2] selftests: drv-net: add helper for path resolution
https://git.kernel.org/netdev/net-next/c/3337064f4204
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-02-11 3:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 18:41 [PATCH net-next 1/2] selftests: drv-net: factor out a DrvEnv base class Jakub Kicinski
2025-02-07 18:41 ` [PATCH net-next 2/2] selftests: drv-net: add helper for path resolution Jakub Kicinski
2025-02-10 14:24 ` Petr Machata
2025-02-10 14:24 ` [PATCH net-next 1/2] selftests: drv-net: factor out a DrvEnv base class Petr Machata
2025-02-11 3:30 ` 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=173924464474.3948401.15014700951334326245.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=sdf@fomichev.me \
--cc=shuah@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;
as well as URLs for NNTP newsgroup(s).