From: patchwork-bot+netdevbpf@kernel.org
To: Wang Liang <wangliang74@huawei.com>
Cc: kuba@kernel.org, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, shuah@kernel.org,
acardace@redhat.com, netdev@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
yuehaibing@huawei.com, zhangchangzhong@huawei.com
Subject: Re: [PATCH net v2] selftests: netdevsim: Fix ethtool-coalesce.sh fail by installing ethtool-common.sh
Date: Sat, 01 Nov 2025 00:50:11 +0000 [thread overview]
Message-ID: <176195821124.682052.16276710639901642661.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251030040340.3258110-1-wangliang74@huawei.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 30 Oct 2025 12:03:40 +0800 you wrote:
> The script "ethtool-common.sh" is not installed in INSTALL_PATH, and
> triggers some errors when I try to run the test
> 'drivers/net/netdevsim/ethtool-coalesce.sh':
>
> TAP version 13
> 1..1
> # timeout set to 600
> # selftests: drivers/net/netdevsim: ethtool-coalesce.sh
> # ./ethtool-coalesce.sh: line 4: ethtool-common.sh: No such file or directory
> # ./ethtool-coalesce.sh: line 25: make_netdev: command not found
> # ethtool: bad command line argument(s)
> # ./ethtool-coalesce.sh: line 124: check: command not found
> # ./ethtool-coalesce.sh: line 126: [: -eq: unary operator expected
> # FAILED /0 checks
> not ok 1 selftests: drivers/net/netdevsim: ethtool-coalesce.sh # exit=1
>
> [...]
Here is the summary with links:
- [net,v2] selftests: netdevsim: Fix ethtool-coalesce.sh fail by installing ethtool-common.sh
https://git.kernel.org/netdev/net/c/d01f8136d46b
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-11-01 0:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 4:03 Wang Liang
2025-11-01 0:50 ` 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=176195821124.682052.16276710639901642661.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=acardace@redhat.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=wangliang74@huawei.com \
--cc=yuehaibing@huawei.com \
--cc=zhangchangzhong@huawei.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
all inboxes | Powered by JetHome®