From: Ido Schimmel <idosch@idosch.org>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, jiri@nvidia.com,
danieller@nvidia.com, mlxsw@nvidia.com,
Ido Schimmel <idosch@nvidia.com>
Subject: [PATCH net 0/2] mlxsw: Various fixes
Date: Thu, 28 Jan 2021 16:48:18 +0200 [thread overview]
Message-ID: <20210128144820.3280295-1-idosch@idosch.org> (raw)
From: Ido Schimmel <idosch@nvidia.com>
Patch #1 fixes wrong invocation of mausezahn in a couple of selftests.
The tests started failing after Fedora updated their libnet package from
version 1.1.6 to 1.2.1. With the fix the tests pass regardless of libnet
version.
Patch #2 fixes an issue in the mirroring to CPU code that results in
policer configuration being overwritten.
Danielle Ratson (1):
selftests: forwarding: Specify interface when invoking mausezahn
Ido Schimmel (1):
mlxsw: spectrum_span: Do not overwrite policer configuration
drivers/net/ethernet/mellanox/mlxsw/spectrum_span.c | 6 ++++++
drivers/net/ethernet/mellanox/mlxsw/spectrum_span.h | 1 +
tools/testing/selftests/net/forwarding/router_mpath_nh.sh | 2 +-
tools/testing/selftests/net/forwarding/router_multipath.sh | 2 +-
4 files changed, 9 insertions(+), 2 deletions(-)
--
2.29.2
next reply other threads:[~2021-01-28 14:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 14:48 Ido Schimmel [this message]
2021-01-28 14:48 ` [PATCH net 1/2] selftests: forwarding: Specify interface when invoking mausezahn Ido Schimmel
2021-01-28 14:48 ` [PATCH net 2/2] mlxsw: spectrum_span: Do not overwrite policer configuration Ido Schimmel
2021-01-28 21:20 ` [PATCH net 0/2] mlxsw: Various fixes patchwork-bot+netdevbpf
-- strict thread matches above, loose matches on Subject: below --
2020-07-10 13:41 Ido Schimmel
2020-07-10 21:34 ` David Miller
2020-05-21 12:11 Ido Schimmel
2020-05-22 23:08 ` David Miller
2019-03-12 8:40 Ido Schimmel
2019-03-12 21:55 ` David Miller
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=20210128144820.3280295-1-idosch@idosch.org \
--to=idosch@idosch.org \
--cc=danieller@nvidia.com \
--cc=davem@davemloft.net \
--cc=idosch@nvidia.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--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).