From: patchwork-bot+netdevbpf@kernel.org
To: Yujie Liu <yujie.liu@intel.com>
Cc: netdev@vger.kernel.org, liuhangbin@gmail.com, pabeni@redhat.com,
dsahern@kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, lkp@intel.com,
oliver.sang@intel.com
Subject: Re: [PATCH v2 net-next] selftests/net: change shebang to bash to support "source"
Date: Thu, 04 Jan 2024 01:10:25 +0000 [thread overview]
Message-ID: <170433062564.12007.6147887260840109226.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231229131931.3961150-1-yujie.liu@intel.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 29 Dec 2023 21:19:31 +0800 you wrote:
> The patch set [1] added a general lib.sh in net selftests, and converted
> several test scripts to source the lib.sh.
>
> unicast_extensions.sh (converted in [1]) and pmtu.sh (converted in [2])
> have a /bin/sh shebang which may point to various shells in different
> distributions, but "source" is only available in some of them. For
> example, "source" is a built-it function in bash, but it cannot be
> used in dash.
>
> [...]
Here is the summary with links:
- [v2,net-next] selftests/net: change shebang to bash to support "source"
https://git.kernel.org/netdev/net-next/c/05d92cb0e919
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:[~2024-01-04 1:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-29 13:19 [PATCH v2 net-next] selftests/net: change shebang to bash to support "source" Yujie Liu
2023-12-29 15:19 ` Przemek Kitszel
2023-12-30 6:20 ` Hangbin Liu
2023-12-30 6:30 ` Muhammad Usama Anjum
2023-12-31 12:17 ` Guillaume Nault
2024-01-02 5:51 ` Yujie Liu
2024-01-02 6:51 ` Hangbin Liu
2024-01-02 8:20 ` Yujie Liu
2024-01-02 11:32 ` Guillaume Nault
2023-12-31 16:27 ` Guillaume Nault
2024-01-04 1: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=170433062564.12007.6147887260840109226.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=dsahern@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=oliver.sang@intel.com \
--cc=pabeni@redhat.com \
--cc=yujie.liu@intel.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).