Netdev List
 help / color / mirror / Atom feed
From: Michael Chan <michael.chan@broadcom.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, andrew+netdev@lunn.ch,
	pavan.chebbi@broadcom.com, andrew.gospodarek@broadcom.com,
	joe@dama.to
Subject: [PATCH net v3 0/3] bnxt_en: PCIe FLR/AER fixes
Date: Mon,  5 Oct 2026 13:42:43 -0700	[thread overview]
Message-ID: <20261005204246.3822563-1-michael.chan@broadcom.com> (raw)

This patchset is split from the earlier 9-patch series to limit the
fixes to the PCIe FLR/AER issues only (patches 7 to 9).  The other
fixes (patches 1 to 6) will be sent to net-next separately.

The 1st patch is unchanged since v1.  It refactors a bnxt_clear_bars()
helper needed by patch 2 and 3.  Patch 2 fixes an issue during driver
init.  in the kdump kernel on a Dell system with a smart PCIe switch
upstream from the NIC.  Patch 3 fixes an issue in the AER code path for
non-fatal errors found by a partner.

These patches have been regression tested on Broadcom 5750X and 5760X
NICs running 237.x.x.x production FW.

v3:
Only include the 3 PCIe FLR/AER fixes.
Updated to address some more Sashiko comments.

v2:
Updated to address some Sashiko comments.

https://lore.kernel.org/netdev/20260928041712.3467803-1-michael.chan@broadcom.com/

v1:
https://lore.kernel.org/netdev/20260831024342.2161156-1-michael.chan@broadcom.com/

Michael Chan (2):
  bnxt_en: Add bnxt_clear_bars() helper
  bnxt_en: Fix driver init in kdump kernel

Pavan Chebbi (1):
  bnxt_en: Re-write the BARs following any type of PCIe errors

 drivers/net/ethernet/broadcom/bnxt/bnxt.c | 164 ++++++++++++++--------
 drivers/net/ethernet/broadcom/bnxt/bnxt.h |   1 -
 2 files changed, 108 insertions(+), 57 deletions(-)

-- 
2.51.0


             reply	other threads:[~2026-10-05 20:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-05 20:42 Michael Chan [this message]
2026-10-05 20:42 ` [PATCH net v3 1/3] bnxt_en: Add bnxt_clear_bars() helper Michael Chan
2026-10-05 20:42 ` [PATCH net v3 2/3] bnxt_en: Fix driver init in kdump kernel Michael Chan
2026-10-07 20:44   ` netdev-bot+sashiko
2026-10-07 21:20     ` Michael Chan
2026-10-05 20:42 ` [PATCH net v3 3/3] bnxt_en: Re-write the BARs following any type of PCIe errors Michael Chan
2026-10-07 20:44   ` netdev-bot+sashiko
2026-10-06 21:32 ` [PATCH net v3 0/3] bnxt_en: PCIe FLR/AER fixes Jacob Keller
2026-10-08  1:00 ` 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=20261005204246.3822563-1-michael.chan@broadcom.com \
    --to=michael.chan@broadcom.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=andrew.gospodarek@broadcom.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=joe@dama.to \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pavan.chebbi@broadcom.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