From: David Miller <davem@davemloft.net>
To: petrm@mellanox.com
Cc: netdev@vger.kernel.org, linux-mlxsw@lists.ozlabs.org
Subject: Re: [PATCH net-next 0/7] selftests: Add tests for mirroring to gretap
Date: Fri, 27 Apr 2018 14:58:12 -0400 (EDT) [thread overview]
Message-ID: <20180427.145812.1468618829590253773.davem@davemloft.net> (raw)
In-Reply-To: <cover.1524784510.git.petrm@mellanox.com>
From: Petr Machata <petrm@mellanox.com>
Date: Fri, 27 Apr 2018 01:17:05 +0200
> This suite tests GRE-encapsulated mirroring. The general topology that
> most of the tests use is as follows, but each test defines details of
> the topology based on its needs, and some tests actually use a somewhat
> different topology.
Always good to see more networking tests.
Series applied, thanks.
prev parent reply other threads:[~2018-04-27 18:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 23:17 [PATCH net-next 0/7] selftests: Add tests for mirroring to gretap Petr Machata
2018-04-26 23:17 ` [PATCH net-next 1/7] selftests: forwarding: Add libs for gretap mirror testing Petr Machata
2018-04-26 23:18 ` [PATCH net-next 2/7] selftests: forwarding: Add test for mirror to gretap Petr Machata
2018-04-26 23:19 ` [PATCH net-next 3/7] selftests: forwarding: Test gretap mirror with next-hop remote Petr Machata
2018-04-26 23:19 ` [PATCH net-next 4/7] selftests: forwarding: Test mirror to gretap w/ bound dev Petr Machata
2018-04-26 23:20 ` [PATCH net-next 5/7] selftests: forwarding: Test flower mirror to gretap Petr Machata
2018-04-26 23:21 ` [PATCH net-next 6/7] selftests: forwarding: Test neighbor updates when mirroring " Petr Machata
2018-04-26 23:22 ` [PATCH net-next 7/7] selftests: forwarding: Test changes in mirror-to-gretap Petr Machata
2018-04-27 18:58 ` David Miller [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=20180427.145812.1468618829590253773.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-mlxsw@lists.ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=petrm@mellanox.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).