netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 0/8] mlxsw, selftests: Cleanups
Date: Fri, 2 Jun 2023 18:20:04 +0200	[thread overview]
Message-ID: <cover.1685720841.git.petrm@nvidia.com> (raw)

This patchset consolidates a number of disparate items that can all be
considered cleanups. They are all related to mlxsw in that they are
directly in mlxsw code, or in selftests that mlxsw heavily uses.

- patch #1 fixes a comment, patch #2 propagates an extack

- patches #3 and #4 tweak several loops to query a resource once and cache
  in a local variable instead of querying on each iteration

- patches #5 and #6 fix selftest diagrams, and #7 adds a missing diagram
  into an existing test

- patch #8 disables a PVID on a bridge in a selftest that should not need
  said PVID

Petr Machata (8):
  mlxsw: spectrum_router: Clarify a comment
  mlxsw: spectrum_router: Use extack in
    mlxsw_sp~_rif_ipip_lb_configure()
  mlxsw: spectrum_router: Do not query MAX_RIFS on each iteration
  mlxsw: spectrum_router: Do not query MAX_VRS on each iteration
  selftests: mlxsw: ingress_rif_conf_1d: Fix the diagram
  selftests: mlxsw: egress_vid_classification: Fix the diagram
  selftests: router_bridge_vlan: Add a diagram
  selftests: router_bridge_vlan: Set vlan_default_pvid 0 on the bridge

 .../ethernet/mellanox/mlxsw/spectrum_router.c | 26 ++++++++++++-------
 .../net/mlxsw/egress_vid_classification.sh    |  5 ++--
 .../drivers/net/mlxsw/ingress_rif_conf_1d.sh  |  5 ++--
 .../net/forwarding/router_bridge_vlan.sh      | 24 ++++++++++++++++-
 4 files changed, 43 insertions(+), 17 deletions(-)

-- 
2.40.1


             reply	other threads:[~2023-06-02 16:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-02 16:20 Petr Machata [this message]
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 ` [PATCH net-next 5/8] selftests: mlxsw: ingress_rif_conf_1d: Fix the diagram Petr Machata
2023-06-02 16:20 ` [PATCH net-next 6/8] selftests: mlxsw: egress_vid_classification: " 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=cover.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;
as well as URLs for NNTP newsgroup(s).