From: patchwork-bot+netdevbpf@kernel.org
To: Michael Chan <michael.chan@broadcom.com>
Cc: davem@davemloft.net, 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: Re: [PATCH net v3 0/3] bnxt_en: PCIe FLR/AER fixes
Date: Thu, 08 Oct 2026 01:00:07 +0000 [thread overview]
Message-ID: <179142120734.3755089.17211132797892380452.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261005204246.3822563-1-michael.chan@broadcom.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 5 Oct 2026 13:42:43 -0700 you wrote:
> 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.
>
> [...]
Here is the summary with links:
- [net,v3,1/3] bnxt_en: Add bnxt_clear_bars() helper
https://git.kernel.org/netdev/net/c/8f5d59b9cfa6
- [net,v3,2/3] bnxt_en: Fix driver init in kdump kernel
https://git.kernel.org/netdev/net/c/386f887c8290
- [net,v3,3/3] bnxt_en: Re-write the BARs following any type of PCIe errors
https://git.kernel.org/netdev/net/c/2e52da27096d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-10-08 1:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 20:42 [PATCH net v3 0/3] bnxt_en: PCIe FLR/AER fixes Michael Chan
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 [this message]
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=179142120734.3755089.17211132797892380452.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--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=michael.chan@broadcom.com \
--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