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,
shuah@kernel.org, willemb@google.com, noren@nvidia.com,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] selftests: drv-net: Fix and improve command requirement checking
Date: Fri, 25 Jul 2025 02:00:25 +0000 [thread overview]
Message-ID: <175340882599.2604761.7778521635617787106.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250723135454.649342-1-gal@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 23 Jul 2025 16:54:52 +0300 you wrote:
> This series fixes remote command checking and cleans up command
> requirement calls across tests.
>
> The first patch fixes require_cmd() incorrectly checking commands
> locally even when remote=True was specified due to a missing host
> parameter.
>
> [...]
Here is the summary with links:
- [net-next,1/2] selftests: drv-net: Fix remote command checking in require_cmd()
https://git.kernel.org/netdev/net-next/c/b4d52c698210
- [net-next,2/2] selftests: drv-net: Make command requirements explicit
https://git.kernel.org/netdev/net-next/c/d74cd9a02f02
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-07-25 2:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 13:54 [PATCH net-next 0/2] selftests: drv-net: Fix and improve command requirement checking Gal Pressman
2025-07-23 13:54 ` [PATCH net-next 1/2] selftests: drv-net: Fix remote command checking in require_cmd() Gal Pressman
2025-07-23 13:54 ` [PATCH net-next 2/2] selftests: drv-net: Make command requirements explicit Gal Pressman
2025-07-25 2:00 ` 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=175340882599.2604761.7778521635617787106.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=gal@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=noren@nvidia.com \
--cc=pabeni@redhat.com \
--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