From: David Ahern <dsahern@gmail.com>
To: Ido Schimmel <idosch@idosch.org>
Cc: netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
idosch@mellanox.com, jiri@mellanox.com
Subject: Re: [PATCH net-next 2/5] selftests: forwarding: Only check for mz when it is needed
Date: Thu, 1 Mar 2018 14:44:11 -0700 [thread overview]
Message-ID: <5f0c7d0e-b7a7-ee38-3965-8754f17d9505@gmail.com> (raw)
In-Reply-To: <20180301193618.GB4839@splinter>
On 3/1/18 12:36 PM, Ido Schimmel wrote:
> On Thu, Mar 01, 2018 at 11:09:44AM -0800, David Ahern wrote:
>> Add a CHECK_MZ flag and only check if mz exists when flag is set.
>> If it does not exist, exit non-0.
>>
>> Signed-off-by: David Ahern <dsahern@gmail.com>
>
> The only test that doesn't require it is router.sh so I'm not sure it's
> worth the effort. If you still want to keep the patch then
> bridge_vlan_aware.sh needs to be patched as well.
>
ok, I'll drop this one
next prev parent reply other threads:[~2018-03-01 21:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 19:09 [PATCH net-next 0/5] selftests: forwarding: misc bug fixes and enhancements David Ahern
2018-03-01 19:09 ` [PATCH net-next 1/5] selftests: forwarding: Only check tc version for tc tests David Ahern
2018-03-01 20:12 ` Ido Schimmel
2018-03-01 19:09 ` [PATCH net-next 2/5] selftests: forwarding: Only check for mz when it is needed David Ahern
2018-03-01 19:36 ` Ido Schimmel
2018-03-01 21:44 ` David Ahern [this message]
2018-03-01 19:09 ` [PATCH net-next 3/5] selftests: forwarding: Handle 0 for packet difference in multipath tests David Ahern
2018-03-01 19:37 ` Ido Schimmel
2018-03-01 19:09 ` [PATCH net-next 4/5] selftests: forwarding: Use PING6 instead of ping for ipv6 multipath test David Ahern
2018-03-01 19:39 ` Ido Schimmel
2018-03-01 19:43 ` David Ahern
2018-03-01 19:49 ` Ido Schimmel
2018-03-01 19:09 ` [PATCH net-next 5/5] selftests: forwarding: Add description to the multipath tests David Ahern
2018-03-01 19:43 ` Ido Schimmel
2018-03-01 19:27 ` [PATCH net-next 0/5] selftests: forwarding: misc bug fixes and enhancements Ido Schimmel
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=5f0c7d0e-b7a7-ee38-3965-8754f17d9505@gmail.com \
--to=dsahern@gmail.com \
--cc=idosch@idosch.org \
--cc=idosch@mellanox.com \
--cc=jiri@mellanox.com \
--cc=linux-kselftest@vger.kernel.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 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).