From: Petr Machata <petrm@nvidia.com>
To: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
<netdev@vger.kernel.org>
Cc: Petr Machata <petrm@nvidia.com>,
Danielle Ratson <danieller@nvidia.com>, <mlxsw@nvidia.com>
Subject: [PATCH net-next 0/4] selftests: mlxsw: Convert to iproute2 dcb
Date: Mon, 30 Jan 2023 17:40:00 +0100 [thread overview]
Message-ID: <cover.1675096231.git.petrm@nvidia.com> (raw)
There is a dedicated tool for configuration of DCB in iproute2. Use it
in the selftests instead of lldpad.
Patches #1-#3 convert three tests. Patch #4 drops the now-unnecessary
lldpad helpers.
Petr Machata (4):
selftests: mlxsw: qos_dscp_bridge: Convert from lldptool to dcb
selftests: mlxsw: qos_dscp_router: Convert from lldptool to dcb
selftests: mlxsw: qos_defprio: Convert from lldptool to dcb
selftests: net: forwarding: lib: Drop lldpad_app_wait_set(), _del()
.../drivers/net/mlxsw/qos_defprio.sh | 68 +++++--------------
.../drivers/net/mlxsw/qos_dscp_bridge.sh | 23 ++-----
.../drivers/net/mlxsw/qos_dscp_router.sh | 27 ++------
tools/testing/selftests/net/forwarding/lib.sh | 21 ------
4 files changed, 27 insertions(+), 112 deletions(-)
--
2.39.0
next reply other threads:[~2023-01-30 16:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 16:40 Petr Machata [this message]
2023-01-30 16:40 ` [PATCH net-next 1/4] selftests: mlxsw: qos_dscp_bridge: Convert from lldptool to dcb Petr Machata
2023-01-30 16:40 ` [PATCH net-next 2/4] selftests: mlxsw: qos_dscp_router: " Petr Machata
2023-01-30 16:40 ` [PATCH net-next 3/4] selftests: mlxsw: qos_defprio: " Petr Machata
2023-01-30 16:40 ` [PATCH net-next 4/4] selftests: net: forwarding: lib: Drop lldpad_app_wait_set(), _del() Petr Machata
2023-02-01 5:10 ` [PATCH net-next 0/4] selftests: mlxsw: Convert to iproute2 dcb patchwork-bot+netdevbpf
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=cover.1675096231.git.petrm@nvidia.com \
--to=petrm@nvidia.com \
--cc=danieller@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).