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: Ido Schimmel <idosch@nvidia.com>, Petr Machata <petrm@nvidia.com>,
"Amit Cohen" <amcohen@nvidia.com>,
Danielle Ratson <danieller@nvidia.com>,
<linux-kselftest@vger.kernel.org>, <mlxsw@nvidia.com>
Subject: [PATCH net-next 5/8] selftests: mlxsw: ingress_rif_conf_1d: Fix the diagram
Date: Fri, 2 Jun 2023 18:20:09 +0200 [thread overview]
Message-ID: <00eb8e5f01883f35852fc49fbd625f2b5fd566ce.1685720841.git.petrm@nvidia.com> (raw)
In-Reply-To: <cover.1685720841.git.petrm@nvidia.com>
The topology diagram implies that $swp1 and $swp2 are members of the bridge
br0, when in fact only their uppers, $swp1.10 and $swp2.10 are. Adjust the
diagram.
Signed-off-by: Petr Machata <petrm@nvidia.com>
Reviewed-by: Amit Cohen <amcohen@nvidia.com>
---
.../selftests/drivers/net/mlxsw/ingress_rif_conf_1d.sh | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/tools/testing/selftests/drivers/net/mlxsw/ingress_rif_conf_1d.sh b/tools/testing/selftests/drivers/net/mlxsw/ingress_rif_conf_1d.sh
index df2b09966886..7d7f862c809c 100755
--- a/tools/testing/selftests/drivers/net/mlxsw/ingress_rif_conf_1d.sh
+++ b/tools/testing/selftests/drivers/net/mlxsw/ingress_rif_conf_1d.sh
@@ -15,10 +15,9 @@
# +----------------|--+ +--|-----------------+
# | |
# +----------------|-------------------------|-----------------+
-# | SW | | |
+# | SW $swp1 + + $swp2 |
+# | | | |
# | +--------------|-------------------------|---------------+ |
-# | | $swp1 + + $swp2 | |
-# | | | | | |
# | | $swp1.10 + + $swp2.10 | |
# | | | |
# | | br0 | |
--
2.40.1
next prev parent reply other threads:[~2023-06-02 16:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 16:20 [PATCH net-next 0/8] mlxsw, selftests: Cleanups Petr Machata
2023-06-02 16:20 ` [PATCH net-next 1/8] mlxsw: spectrum_router: Clarify a comment Petr Machata
2023-06-02 16:20 ` [PATCH net-next 2/8] mlxsw: spectrum_router: Use extack in mlxsw_sp~_rif_ipip_lb_configure() Petr Machata
2023-06-02 16:20 ` [PATCH net-next 3/8] mlxsw: spectrum_router: Do not query MAX_RIFS on each iteration Petr Machata
2023-06-02 16:20 ` [PATCH net-next 4/8] mlxsw: spectrum_router: Do not query MAX_VRS " Petr Machata
2023-06-02 16:20 ` Petr Machata [this message]
2023-06-02 16:20 ` [PATCH net-next 6/8] selftests: mlxsw: egress_vid_classification: Fix the diagram Petr Machata
2023-06-02 16:20 ` [PATCH net-next 7/8] selftests: router_bridge_vlan: Add a diagram Petr Machata
2023-06-02 16:20 ` [PATCH net-next 8/8] selftests: router_bridge_vlan: Set vlan_default_pvid 0 on the bridge Petr Machata
2023-06-05 10:30 ` [PATCH net-next 0/8] mlxsw, selftests: Cleanups 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=00eb8e5f01883f35852fc49fbd625f2b5fd566ce.1685720841.git.petrm@nvidia.com \
--to=petrm@nvidia.com \
--cc=amcohen@nvidia.com \
--cc=danieller@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.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