From: David Ahern <dsahern@gmail.com>
To: "Tobin C. Harding" <tobin@apporbit.com>
Cc: netdev@vger.kernel.org, Thomas.Winter@alliedtelesis.co.nz,
idosch@mellanox.com, sharpd@cumulusnetworks.com,
roopa@cumulusnetworks.com
Subject: Re: [PATCH RFC net-next 0/7] net/ipv6: Fix route append and replace use cases
Date: Tue, 15 May 2018 00:25:03 -0600 [thread overview]
Message-ID: <34b6b5df-515f-62ed-7135-142b0895e7d1@gmail.com> (raw)
In-Reply-To: <20180515061231.GC10152@eros>
On 5/15/18 12:12 AM, Tobin C. Harding wrote:
> Queue questions on how to run your selftests ;)
copy tools/testing/selftests/net/fib_tests.sh to test environment.
Run it with no options to run all tests or to run specific tests:
$ fib_tests.sh -t ipv4_rt
$ fib_tests.sh -t ipv6_rt
next prev parent reply other threads:[~2018-05-15 6:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 2:51 [PATCH RFC net-next 0/7] net/ipv6: Fix route append and replace use cases David Ahern
2018-05-15 2:51 ` [PATCH RFC net-next 1/7] mlxsw: spectrum_router: Add support for route append David Ahern
2018-05-15 2:51 ` [PATCH RFC net-next 2/7] net/ipv6: Simplify route replace and appending into multipath route David Ahern
2018-05-15 2:51 ` [PATCH RFC net-next 3/7] selftests: fib_tests: Add success-fail counts David Ahern
2018-05-15 2:51 ` [PATCH RFC net-next 4/7] selftests: fib_tests: Add command line options David Ahern
2018-05-15 2:51 ` [PATCH RFC net-next 5/7] selftests: fib_tests: Add option to pause after each test David Ahern
2018-05-15 2:51 ` [PATCH RFC net-next 6/7] selftests: fib_tests: Add ipv6 route add append replace tests David Ahern
2018-05-15 2:51 ` [PATCH RFC net-next 7/7] selftests: fib_tests: Add ipv4 " David Ahern
2018-05-15 5:21 ` [PATCH RFC net-next 0/7] net/ipv6: Fix route append and replace use cases Tobin C. Harding
2018-05-15 5:54 ` David Ahern
2018-05-15 6:12 ` Tobin C. Harding
2018-05-15 6:25 ` David Ahern [this message]
2018-05-15 6:38 ` Tobin C. Harding
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=34b6b5df-515f-62ed-7135-142b0895e7d1@gmail.com \
--to=dsahern@gmail.com \
--cc=Thomas.Winter@alliedtelesis.co.nz \
--cc=idosch@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.com \
--cc=sharpd@cumulusnetworks.com \
--cc=tobin@apporbit.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.