From: David Ahern <dsahern@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>, David Miller <davem@davemloft.net>
Cc: schoen@loyalty.org, "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH 00/11] selftests: Updates to allow single instance of nettest for client and server
Date: Sat, 9 Jan 2021 11:55:39 -0700 [thread overview]
Message-ID: <036b819f-57ad-972e-6728-b1ef87a31efe@gmail.com> (raw)
In-Reply-To: <20210109185358.34616-1-dsahern@kernel.org>
On 1/9/21 11:53 AM, David Ahern wrote:
> Update nettest to handle namespace change internally to allow a
> single instance to run both client and server modes. Device validation
> needs to be moved after the namespace change and a few run time
> options need to be split to allow values for client and server.
>
> David Ahern (11):
> selftests: Move device validation in nettest
> selftests: Move convert_addr up in nettest
> selftests: Move address validation in nettest
> selftests: Add options to set network namespace to nettest
> selftests: Add support to nettest to run both client and server
> selftests: Use separate stdout and stderr buffers in nettest
> selftests: Add missing newline in nettest error messages
> selftests: Make address validation apply only to client mode
> selftests: Consistently specify address for MD5 protection
> selftests: Add new option for client-side passwords
> selftests: Add separate options for server device bindings
>
> tools/testing/selftests/net/fcnal-test.sh | 398 +++++++--------
> tools/testing/selftests/net/nettest.c | 576 +++++++++++++++-------
> 2 files changed, 595 insertions(+), 379 deletions(-)
>
Ugh, I forgot to add net-next to the subject line. Let me know if I
should re-send.
next prev parent reply other threads:[~2021-01-09 18:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-09 18:53 [PATCH 00/11] selftests: Updates to allow single instance of nettest for client and server David Ahern
2021-01-09 18:53 ` [PATCH 01/11] selftests: Move device validation in nettest David Ahern
2021-01-09 18:53 ` [PATCH 02/11] selftests: Move convert_addr up " David Ahern
2021-01-09 18:53 ` [PATCH 03/11] selftests: Move address validation " David Ahern
2021-01-09 18:53 ` [PATCH 04/11] selftests: Add options to set network namespace to nettest David Ahern
2021-01-09 18:53 ` [PATCH 05/11] selftests: Add support to nettest to run both client and server David Ahern
2021-01-09 18:53 ` [PATCH 06/11] selftests: Use separate stdout and stderr buffers in nettest David Ahern
2021-01-09 18:53 ` [PATCH 07/11] selftests: Add missing newline in nettest error messages David Ahern
2021-01-09 18:53 ` [PATCH 08/11] selftests: Make address validation apply only to client mode David Ahern
2021-01-09 18:53 ` [PATCH 09/11] selftests: Consistently specify address for MD5 protection David Ahern
2021-01-09 18:53 ` [PATCH 10/11] selftests: Add new option for client-side passwords David Ahern
2021-01-09 18:53 ` [PATCH 11/11] selftests: Add separate options for server device bindings David Ahern
2021-01-09 18:55 ` David Ahern [this message]
2021-01-09 19:02 ` [PATCH 00/11] selftests: Updates to allow single instance of nettest for client and server Jakub Kicinski
2021-01-09 23:04 ` Jakub Kicinski
2021-01-09 23:12 ` David Ahern
2021-01-09 23:17 ` Jakub Kicinski
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=036b819f-57ad-972e-6728-b1ef87a31efe@gmail.com \
--to=dsahern@gmail.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=schoen@loyalty.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 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).