All of lore.kernel.org
 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: Jacob Keller <jacob.e.keller@intel.com>,
	Ido Schimmel <idosch@nvidia.com>, Petr Machata <petrm@nvidia.com>,
	Jiri Pirko <jiri@nvidia.com>,
	"Danielle Ratson" <danieller@nvidia.com>, <mlxsw@nvidia.com>
Subject: [PATCH net-next 0/6] mlxsw: Misc devlink changes
Date: Mon, 6 Feb 2023 16:39:17 +0100	[thread overview]
Message-ID: <cover.1675692666.git.petrm@nvidia.com> (raw)

This patchset adjusts mlxsw to recent devlink changes in net-next.

Patch #1 removes a devl_param_driverinit_value_set() call that was
unnecessary, but now additionally triggers a WARN_ON.

Patches #2-#4 are non-functional preparations for the following patches.

Patch #5 fixes a use-after-free that is triggered while changing network
namespaces.

Patch #6 makes mlxsw consistent with netdevsim by having mlxsw register
its devlink instance before its sub-objects. It helps us avoid a warning
described in the commit message.

Danielle Ratson (1):
  mlxsw: spectrum: Remove pointless call to
    devlink_param_driverinit_value_set()

Ido Schimmel (5):
  mlxsw: spectrum_acl_tcam: Add missing mutex_destroy()
  mlxsw: spectrum_acl_tcam: Make fini symmetric to init
  mlxsw: spectrum_acl_tcam: Reorder functions to avoid forward
    declarations
  mlxsw: spectrum_acl_tcam: Move devlink param to TCAM code
  mlxsw: core: Register devlink instance before sub-objects

 drivers/net/ethernet/mellanox/mlxsw/core.c    |  31 +--
 drivers/net/ethernet/mellanox/mlxsw/core.h    |   2 -
 .../net/ethernet/mellanox/mlxsw/spectrum.c    |  62 -----
 .../net/ethernet/mellanox/mlxsw/spectrum.h    |   3 +-
 .../ethernet/mellanox/mlxsw/spectrum_acl.c    |  21 +-
 .../mellanox/mlxsw/spectrum_acl_tcam.c        | 244 +++++++++++-------
 .../mellanox/mlxsw/spectrum_acl_tcam.h        |   5 -
 7 files changed, 161 insertions(+), 207 deletions(-)

-- 
2.39.0


             reply	other threads:[~2023-02-06 15:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-06 15:39 Petr Machata [this message]
2023-02-06 15:39 ` [PATCH net-next 1/6] mlxsw: spectrum: Remove pointless call to devlink_param_driverinit_value_set() Petr Machata
2023-02-07  7:39   ` Jiri Pirko
2023-02-06 15:39 ` [PATCH net-next 2/6] mlxsw: spectrum_acl_tcam: Add missing mutex_destroy() Petr Machata
2023-02-06 15:39 ` [PATCH net-next 3/6] mlxsw: spectrum_acl_tcam: Make fini symmetric to init Petr Machata
2023-02-06 15:39 ` [PATCH net-next 4/6] mlxsw: spectrum_acl_tcam: Reorder functions to avoid forward declarations Petr Machata
2023-02-06 15:39 ` [PATCH net-next 5/6] mlxsw: spectrum_acl_tcam: Move devlink param to TCAM code Petr Machata
2023-02-06 15:39 ` [PATCH net-next 6/6] mlxsw: core: Register devlink instance before sub-objects Petr Machata
2023-02-06 17:41 ` [PATCH net-next 0/6] mlxsw: Misc devlink changes Jacob Keller
2023-02-08  4:30 ` 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.1675692666.git.petrm@nvidia.com \
    --to=petrm@nvidia.com \
    --cc=danieller@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=idosch@nvidia.com \
    --cc=jacob.e.keller@intel.com \
    --cc=jiri@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.