From: David Ahern <dsahern@gmail.com>
To: netdev@vger.kernel.org
Cc: idosch@idosch.org, David Ahern <dsahern@gmail.com>
Subject: [PATCH v3 net-next 4/5] selftests: fib_tests: Allow user to run a specific test
Date: Tue, 6 Mar 2018 19:58:40 -0800 [thread overview]
Message-ID: <20180307035841.774-5-dsahern@gmail.com> (raw)
In-Reply-To: <20180307035841.774-1-dsahern@gmail.com>
Allow a user to run just a specific fib test by setting the TEST
environment variable.
Signed-off-by: David Ahern <dsahern@gmail.com>
---
tools/testing/selftests/net/fib_tests.sh | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/tools/testing/selftests/net/fib_tests.sh b/tools/testing/selftests/net/fib_tests.sh
index 953254439e39..cfdeb35bfed5 100755
--- a/tools/testing/selftests/net/fib_tests.sh
+++ b/tools/testing/selftests/net/fib_tests.sh
@@ -392,9 +392,13 @@ fib_carrier_test()
fib_test()
{
- fib_unreg_test
- fib_down_test
- fib_carrier_test
+ if [ -n "$TEST" ]; then
+ eval $TEST
+ else
+ fib_unreg_test
+ fib_down_test
+ fib_carrier_test
+ fi
}
if [ "$(id -u)" -ne 0 ];then
--
2.11.0
next prev parent reply other threads:[~2018-03-07 3:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 3:58 [PATCH v3 net-next 0/5] net/ipv6: Address checks need to consider the L3 domain David Ahern
2018-03-07 3:58 ` [PATCH v3 net-next 1/5] net/ipv6: Refactor gateway validation on route add David Ahern
2018-03-07 3:58 ` [PATCH v3 net-next 2/5] net/ipv6: Address checks need to consider the L3 domain David Ahern
2018-03-07 11:53 ` Kirill Tkhai
2018-03-07 11:59 ` Kirill Tkhai
2018-03-07 17:28 ` David Ahern
2018-03-07 19:53 ` David Ahern
2018-03-07 3:58 ` [PATCH v3 net-next 3/5] selftests: fib_tests: Use an alias for ip command David Ahern
2018-03-07 3:58 ` David Ahern [this message]
2018-03-07 3:58 ` [PATCH v3 net-next 5/5] selftests: fib_tests: Add IPv6 nexthop spec tests David Ahern
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=20180307035841.774-5-dsahern@gmail.com \
--to=dsahern@gmail.com \
--cc=idosch@idosch.org \
--cc=netdev@vger.kernel.org \
/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.