All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ido Schimmel <idosch@nvidia.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, petrm@nvidia.com,
	jiri@nvidia.com, amcohen@nvidia.com, mlxsw@nvidia.com,
	Ido Schimmel <idosch@nvidia.com>
Subject: [PATCH net-next 0/7] mlxsw: Various updates
Date: Thu, 27 Jan 2022 11:02:19 +0200	[thread overview]
Message-ID: <20220127090226.283442-1-idosch@nvidia.com> (raw)

This patchset contains miscellaneous updates for mlxsw. No user visible
changes that I am aware of.

Patches #1-#5 rework registration of internal traps in preparation of
line cards support.

Patch #6 improves driver resilience against a misbehaving device.

Patch #7 prevents the driver from overwriting device internal actions.
See the commit message for more details.

Amit Cohen (1):
  mlxsw: spectrum: Guard against invalid local ports

Ido Schimmel (1):
  mlxsw: spectrum_acl: Allocate default actions for internal TCAM
    regions

Jiri Pirko (5):
  mlxsw: spectrum: Set basic trap groups from an array
  mlxsw: core: Move basic_trap_groups_set() call out of EMAD init code
  mlxsw: core: Move basic trap group initialization from spectrum.c
  mlxsw: core: Move functions to register/unregister array of traps to
    core.c
  mlxsw: core: Consolidate trap groups to a single event group

 drivers/net/ethernet/mellanox/mlxsw/core.c    |  75 +++++++++++--
 drivers/net/ethernet/mellanox/mlxsw/core.h    |  10 +-
 .../net/ethernet/mellanox/mlxsw/core_env.c    |   4 +-
 drivers/net/ethernet/mellanox/mlxsw/reg.h     |   4 +-
 .../net/ethernet/mellanox/mlxsw/resources.h   |   2 +
 .../net/ethernet/mellanox/mlxsw/spectrum.c    | 106 +++---------------
 .../net/ethernet/mellanox/mlxsw/spectrum.h    |   7 ++
 .../mellanox/mlxsw/spectrum2_acl_tcam.c       |  12 +-
 .../ethernet/mellanox/mlxsw/spectrum_ptp.c    |   3 +-
 .../mellanox/mlxsw/spectrum_switchdev.c       |   3 +-
 10 files changed, 116 insertions(+), 110 deletions(-)

-- 
2.33.1


             reply	other threads:[~2022-01-27  9:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27  9:02 Ido Schimmel [this message]
2022-01-27  9:02 ` [PATCH net-next 1/7] mlxsw: spectrum: Set basic trap groups from an array Ido Schimmel
2022-01-27  9:02 ` [PATCH net-next 2/7] mlxsw: core: Move basic_trap_groups_set() call out of EMAD init code Ido Schimmel
2022-01-27  9:02 ` [PATCH net-next 3/7] mlxsw: core: Move basic trap group initialization from spectrum.c Ido Schimmel
2022-01-27  9:02 ` [PATCH net-next 4/7] mlxsw: core: Move functions to register/unregister array of traps to core.c Ido Schimmel
2022-01-27  9:02 ` [PATCH net-next 5/7] mlxsw: core: Consolidate trap groups to a single event group Ido Schimmel
2022-01-27  9:02 ` [PATCH net-next 6/7] mlxsw: spectrum: Guard against invalid local ports Ido Schimmel
2022-01-27  9:02 ` [PATCH net-next 7/7] mlxsw: spectrum_acl: Allocate default actions for internal TCAM regions Ido Schimmel
2022-01-28  3:30 ` [PATCH net-next 0/7] mlxsw: Various updates patchwork-bot+netdevbpf
  -- strict thread matches above, loose matches on Subject: below --
2018-08-09  8:59 Ido Schimmel
2018-08-09 17:37 ` 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=20220127090226.283442-1-idosch@nvidia.com \
    --to=idosch@nvidia.com \
    --cc=amcohen@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=jiri@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=mlxsw@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=petrm@nvidia.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.