All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Machata <petrm@nvidia.com>
To: "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	<nbu-linux-internal@nvidia.com>
Cc: Shuah Khan <shuah@kernel.org>,
	Nikolay Aleksandrov <razor@blackwall.org>,
	Hangbin Liu <liuhangbin@gmail.com>,
	Vladimir Oltean <vladimir.oltean@nxp.com>,
	Benjamin Poirier <bpoirier@nvidia.com>,
	"Ido Schimmel" <idosch@nvidia.com>, Jiri Pirko <jiri@nvidia.com>,
	<linux-kselftest@vger.kernel.org>,
	Petr Machata <petrm@nvidia.com>
Subject: [RFC PATCH net-next mlxsw 04/14] selftests: forwarding: ipip_lib: Do not import lib.sh
Date: Mon, 25 Mar 2024 18:29:11 +0100	[thread overview]
Message-ID: <a4da5e9cd42a34cbace917a048ca71081719d6ac.1711385795.git.petrm@nvidia.com> (raw)
In-Reply-To: <cover.1711385795.git.petrm@nvidia.com>

This library is always sourced in the context where lib.sh has already been
sourced as well. Therefore drop the explicit sourcing and expect the client
to already have done it. This will simplify moving some of the clients to a
different directory.

Signed-off-by: Petr Machata <petrm@nvidia.com>
---
 tools/testing/selftests/net/forwarding/ipip_lib.sh | 1 -
 1 file changed, 1 deletion(-)

diff --git a/tools/testing/selftests/net/forwarding/ipip_lib.sh b/tools/testing/selftests/net/forwarding/ipip_lib.sh
index 30f36a57bae6..01e62c4ac94d 100644
--- a/tools/testing/selftests/net/forwarding/ipip_lib.sh
+++ b/tools/testing/selftests/net/forwarding/ipip_lib.sh
@@ -141,7 +141,6 @@
 # |               $h2 +       |
 # |     192.0.2.18/28         |
 # +---------------------------+
-source lib.sh
 
 h1_create()
 {
-- 
2.43.0


  parent reply	other threads:[~2024-03-25 17:32 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-25 17:29 [RFC PATCH net-next mlxsw 00/14] selftests: Fixes for kernel CI Petr Machata
2024-03-25 17:29 ` [RFC PATCH net-next mlxsw 01/14] selftests: net: libs: Change variable fallback syntax Petr Machata
2024-03-25 17:29 ` [RFC PATCH net-next mlxsw 02/14] selftests: forwarding.config.sample: Move overrides to lib.sh Petr Machata
2024-03-25 17:29 ` [RFC PATCH net-next mlxsw 03/14] selftests: forwarding: README: Document customization Petr Machata
2024-03-26  0:34   ` Jakub Kicinski
2024-03-26 10:31     ` Petr Machata
2024-03-26 14:13       ` Jakub Kicinski
2024-03-26 17:32         ` Petr Machata
2024-03-25 17:29 ` Petr Machata [this message]
2024-03-25 17:29 ` [RFC PATCH net-next mlxsw 05/14] selftests: forwarding: Move several selftests Petr Machata
2024-03-25 17:29 ` [RFC PATCH net-next mlxsw 06/14] selftests: forwarding: Ditch skip_on_veth() Petr Machata
2024-03-25 17:29 ` [RFC PATCH net-next mlxsw 07/14] selftests: forwarding: Change inappropriate log_test_skip() calls Petr Machata
2024-03-25 17:29 ` [RFC PATCH net-next mlxsw 08/14] selftests: lib: Define more kselftest exit codes Petr Machata
2024-03-25 17:29 ` [RFC PATCH net-next mlxsw 09/14] selftests: forwarding: Have RET track kselftest framework constants Petr Machata
2024-03-26  0:43   ` Jakub Kicinski
2024-03-26 11:12     ` Petr Machata
2024-03-25 17:29 ` [RFC PATCH net-next mlxsw 10/14] selftests: forwarding: Convert log_test() to recognize RET values Petr Machata
2024-03-25 17:29 ` [RFC PATCH net-next mlxsw 11/14] selftests: forwarding: Support for performance sensitive tests Petr Machata
2024-03-25 17:29 ` [RFC PATCH net-next mlxsw 12/14] selftests: forwarding: Mark performance-sensitive tests Petr Machata
2024-03-25 17:29 ` [RFC PATCH net-next mlxsw 13/14] selftests: forwarding: router_mpath_nh_lib: Don't skip, xfail on veth Petr Machata
2024-03-25 17:29 ` [RFC PATCH net-next mlxsw 14/14] selftests: forwarding: Add a test for testing lib.sh functionality Petr Machata
2024-03-26  0:48 ` [RFC PATCH net-next mlxsw 00/14] selftests: Fixes for kernel CI Jakub Kicinski
2024-03-26 11:13   ` Petr Machata

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=a4da5e9cd42a34cbace917a048ca71081719d6ac.1711385795.git.petrm@nvidia.com \
    --to=petrm@nvidia.com \
    --cc=bpoirier@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=idosch@nvidia.com \
    --cc=jiri@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=liuhangbin@gmail.com \
    --cc=nbu-linux-internal@nvidia.com \
    --cc=pabeni@redhat.com \
    --cc=razor@blackwall.org \
    --cc=shuah@kernel.org \
    --cc=vladimir.oltean@nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.