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,
andrew.gospodarek@broadcom.com, shruti.parab@broadcom.com,
hongguang.gao@broadcom.com
Subject: Re: [PATCH net-next v2 00/11] bnxt_en: Add context memory dump to coredump
Date: Tue, 19 Nov 2024 04:00:39 +0000 [thread overview]
Message-ID: <173198883923.97799.4092753376670679738.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241115151438.550106-1-michael.chan@broadcom.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 15 Nov 2024 07:14:26 -0800 you wrote:
> The driver currently supports Live FW dump and crashed FW dump. On
> the newer chips, the driver allocates host backing store context
> memory for the chip and FW to store various states. The content of
> this context memory will be useful for debugging. This patchset
> adds the context memory contents to the ethtool -w coredump using
> a new dump flag.
>
> [...]
Here is the summary with links:
- [net-next,v2,01/11] bnxt_en: Update firmware interface spec to 1.10.3.85
https://git.kernel.org/netdev/net-next/c/ff00bcc9eccc
- [net-next,v2,02/11] bnxt_en: Add mem_valid bit to struct bnxt_ctx_mem_type
https://git.kernel.org/netdev/net-next/c/0b350b4927e6
- [net-next,v2,03/11] bnxt_en: Refactor bnxt_free_ctx_mem()
https://git.kernel.org/netdev/net-next/c/968d2cc07c2f
- [net-next,v2,04/11] bnxt_en: Add a 'force' parameter to bnxt_free_ctx_mem()
https://git.kernel.org/netdev/net-next/c/46010d43ab7b
- [net-next,v2,05/11] bnxt_en: Allocate backing store memory for FW trace logs
https://git.kernel.org/netdev/net-next/c/24d694aec139
- [net-next,v2,06/11] bnxt_en: Manage the FW trace context memory
https://git.kernel.org/netdev/net-next/c/84fcd9449fd7
- [net-next,v2,07/11] bnxt_en: Do not free FW log context memory
https://git.kernel.org/netdev/net-next/c/de999362ad33
- [net-next,v2,08/11] bnxt_en: Add functions to copy host context memory
https://git.kernel.org/netdev/net-next/c/23a18b91b609
- [net-next,v2,09/11] bnxt_en: Add 2 parameters to bnxt_fill_coredump_seg_hdr()
https://git.kernel.org/netdev/net-next/c/a854a17097b9
- [net-next,v2,10/11] bnxt_en: Add a new ethtool -W dump flag
https://git.kernel.org/netdev/net-next/c/bda2e63a508b
- [net-next,v2,11/11] bnxt_en: Add FW trace coredump segments to the coredump
https://git.kernel.org/netdev/net-next/c/3c2179e66355
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:[~2024-11-19 4:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 15:14 [PATCH net-next v2 00/11] bnxt_en: Add context memory dump to coredump Michael Chan
2024-11-15 15:14 ` [PATCH net-next v2 01/11] bnxt_en: Update firmware interface spec to 1.10.3.85 Michael Chan
2024-11-15 15:14 ` [PATCH net-next v2 02/11] bnxt_en: Add mem_valid bit to struct bnxt_ctx_mem_type Michael Chan
2024-11-15 15:14 ` [PATCH net-next v2 03/11] bnxt_en: Refactor bnxt_free_ctx_mem() Michael Chan
2024-11-15 15:14 ` [PATCH net-next v2 04/11] bnxt_en: Add a 'force' parameter to bnxt_free_ctx_mem() Michael Chan
2024-11-15 15:14 ` [PATCH net-next v2 05/11] bnxt_en: Allocate backing store memory for FW trace logs Michael Chan
2024-11-15 15:14 ` [PATCH net-next v2 06/11] bnxt_en: Manage the FW trace context memory Michael Chan
2024-11-15 15:14 ` [PATCH net-next v2 07/11] bnxt_en: Do not free FW log " Michael Chan
2024-11-15 15:14 ` [PATCH net-next v2 08/11] bnxt_en: Add functions to copy host " Michael Chan
2024-11-15 15:14 ` [PATCH net-next v2 09/11] bnxt_en: Add 2 parameters to bnxt_fill_coredump_seg_hdr() Michael Chan
2024-11-15 15:14 ` [PATCH net-next v2 10/11] bnxt_en: Add a new ethtool -W dump flag Michael Chan
2024-11-15 15:14 ` [PATCH net-next v2 11/11] bnxt_en: Add FW trace coredump segments to the coredump Michael Chan
2024-11-19 4: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=173198883923.97799.4092753376670679738.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=hongguang.gao@broadcom.com \
--cc=kuba@kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shruti.parab@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 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.