netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: Petr Machata <petrm@nvidia.com>,
	"David S. Miller" <davem@davemloft.net>,
	 Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>,
	netdev@vger.kernel.org
Cc: Ido Schimmel <idosch@nvidia.com>,
	Danielle Ratson <danieller@nvidia.com>,
	 Amit Cohen <amcohen@nvidia.com>, Jiri Pirko <jiri@resnulli.us>,
	mlxsw@nvidia.com
Subject: Re: [PATCH net 0/6] mlxsw: Miscellaneous fixes
Date: Thu, 18 Jan 2024 16:06:49 +0100	[thread overview]
Message-ID: <1ffdc2fe1956a44ff95f1dd57982836978f3a4e1.camel@redhat.com> (raw)
In-Reply-To: <cover.1705502064.git.petrm@nvidia.com>

On Wed, 2024-01-17 at 16:04 +0100, Petr Machata wrote:
> This patchset is a bric-a-brac of fixes for bugs impacting mlxsw.
> 
> - Patches #1 and #2 fix issues in ACL handling error paths.
> - Patch #3 fixes stack corruption in ACL code that a recent FW update
>   has uncovered.
> 
> - Patch #4 fixes an issue in handling of IPIP next hops.
> 
> - Patch #5 fixes a typo in a the qos_pfc selftest
> - Patch #6 fixes the same selftest to work with 8-lane ports.
> 
> Amit Cohen (3):
>   mlxsw: spectrum_acl_erp: Fix error flow of pool allocation failure
>   selftests: mlxsw: qos_pfc: Remove wrong description
>   selftests: mlxsw: qos_pfc: Adjust the test to support 8 lanes
> 
> Ido Schimmel (2):
>   mlxsw: spectrum_acl_tcam: Fix NULL pointer dereference in error path
>   mlxsw: spectrum_acl_tcam: Fix stack corruption
> 
> Petr Machata (1):
>   mlxsw: spectrum_router: Register netdevice notifier before nexthop
> 
>  .../mellanox/mlxsw/spectrum_acl_erp.c         |   8 +-
>  .../mellanox/mlxsw/spectrum_acl_tcam.c        |   6 +-
>  .../ethernet/mellanox/mlxsw/spectrum_router.c |  24 ++--
>  .../selftests/drivers/net/mlxsw/qos_pfc.sh    |  19 +++-
>  .../drivers/net/mlxsw/spectrum-2/tc_flower.sh | 106 +++++++++++++++++-
>  5 files changed, 143 insertions(+), 20 deletions(-)

LGTM, but still a bit too fresh to be merged right now.

Acked-by: Paolo Abeni <pabeni@redhat.com>


  parent reply	other threads:[~2024-01-18 15:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-17 15:04 [PATCH net 0/6] mlxsw: Miscellaneous fixes Petr Machata
2024-01-17 15:04 ` [PATCH net 1/6] mlxsw: spectrum_acl_erp: Fix error flow of pool allocation failure Petr Machata
2024-01-17 15:04 ` [PATCH net 2/6] mlxsw: spectrum_acl_tcam: Fix NULL pointer dereference in error path Petr Machata
2024-01-17 15:04 ` [PATCH net 3/6] mlxsw: spectrum_acl_tcam: Fix stack corruption Petr Machata
2024-01-17 15:04 ` [PATCH net 4/6] mlxsw: spectrum_router: Register netdevice notifier before nexthop Petr Machata
2024-01-17 15:04 ` [PATCH net 5/6] selftests: mlxsw: qos_pfc: Remove wrong description Petr Machata
2024-01-17 15:04 ` [PATCH net 6/6] selftests: mlxsw: qos_pfc: Adjust the test to support 8 lanes Petr Machata
2024-01-18 15:06 ` Paolo Abeni [this message]
2024-01-18 18:00 ` [PATCH net 0/6] mlxsw: Miscellaneous fixes 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=1ffdc2fe1956a44ff95f1dd57982836978f3a4e1.camel@redhat.com \
    --to=pabeni@redhat.com \
    --cc=amcohen@nvidia.com \
    --cc=danieller@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=idosch@nvidia.com \
    --cc=jiri@resnulli.us \
    --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 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).