From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
alexanderduyck@fb.com, lee@trager.us
Subject: Re: [PATCH net-next v3 0/9] eth: fbnic: add devlink health support for FW crashes and OTP mem corruptions
Date: Thu, 18 Sep 2025 10:20:14 +0000 [thread overview]
Message-ID: <175819081475.2354627.7445984699761115470.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250916231420.1693955-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 16 Sep 2025 16:14:11 -0700 you wrote:
> Add support for FW crash detection and a corresponding devlink health
> reporter. Add a reporter for checking OTP memory health.
>
> The output is not particularly exciting:
>
> # devlink health show
> pci/0000:01:00.0:
> reporter fw
> state healthy error 0 recover 0 auto_dump true
> reporter otp
> state healthy error 0 recover 0 auto_dump true
> # devlink health diagnose pci/0000:01:00.0 reporter fw
> FW uptime: 0
> # devlink health dump show pci/0000:01:00.0 reporter fw
> FW coredump:
> 5a 45 01 00 04 00 06 00 00 00 00 00 4d 01 00 d0
> .. lots of hex follows ..
> # devlink health dump show pci/0000:01:00.0 reporter otp
> OTP:
> Status: 0 Data: 0 ECC: 0
>
> [...]
Here is the summary with links:
- [net-next,v3,1/9] eth: fbnic: make fbnic_fw_log_write() parameter const
https://git.kernel.org/netdev/net-next/c/e6c8ab0a1129
- [net-next,v3,2/9] eth: fbnic: use fw uptime to detect fw crashes
https://git.kernel.org/netdev/net-next/c/7fd1f7bac2b8
- [net-next,v3,3/9] eth: fbnic: factor out clearing the action TCAM
https://git.kernel.org/netdev/net-next/c/504f8b7119eb
- [net-next,v3,4/9] eth: fbnic: reprogram TCAMs after FW crash
https://git.kernel.org/netdev/net-next/c/6ae7da8e9e06
- [net-next,v3,5/9] eth: fbnic: support allocating FW completions with extra space
https://git.kernel.org/netdev/net-next/c/a8896d14fc0c
- [net-next,v3,6/9] eth: fbnic: support FW communication for core dump
https://git.kernel.org/netdev/net-next/c/5df1d0a08483
- [net-next,v3,7/9] eth: fbnic: add FW health reporter
https://git.kernel.org/netdev/net-next/c/005a54722e9d
- [net-next,v3,8/9] eth: fbnic: report FW uptime in health diagnose
https://git.kernel.org/netdev/net-next/c/6da8344f92df
- [net-next,v3,9/9] eth: fbnic: add OTP health reporter
https://git.kernel.org/netdev/net-next/c/e6afcd60c26f
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:[~2025-09-18 10:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 23:14 [PATCH net-next v3 0/9] eth: fbnic: add devlink health support for FW crashes and OTP mem corruptions Jakub Kicinski
2025-09-16 23:14 ` [PATCH net-next v3 1/9] eth: fbnic: make fbnic_fw_log_write() parameter const Jakub Kicinski
2025-09-16 23:14 ` [PATCH net-next v3 2/9] eth: fbnic: use fw uptime to detect fw crashes Jakub Kicinski
2025-09-16 23:14 ` [PATCH net-next v3 3/9] eth: fbnic: factor out clearing the action TCAM Jakub Kicinski
2025-09-16 23:14 ` [PATCH net-next v3 4/9] eth: fbnic: reprogram TCAMs after FW crash Jakub Kicinski
2025-09-16 23:14 ` [PATCH net-next v3 5/9] eth: fbnic: support allocating FW completions with extra space Jakub Kicinski
2025-09-16 23:14 ` [PATCH net-next v3 6/9] eth: fbnic: support FW communication for core dump Jakub Kicinski
2025-09-16 23:14 ` [PATCH net-next v3 7/9] eth: fbnic: add FW health reporter Jakub Kicinski
2025-09-16 23:14 ` [PATCH net-next v3 8/9] eth: fbnic: report FW uptime in health diagnose Jakub Kicinski
2025-09-17 16:08 ` Simon Horman
2025-09-16 23:14 ` [PATCH net-next v3 9/9] eth: fbnic: add OTP health reporter Jakub Kicinski
2025-09-17 16:09 ` Simon Horman
2025-09-18 10:20 ` 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=175819081475.2354627.7445984699761115470.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexanderduyck@fb.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=lee@trager.us \
--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.