From: Kalle Valo <kvalo@codeaurora.org>
To: Ping-Ke Shih <pkshih@realtek.com>
Cc: <tony0620emma@gmail.com>, <linux-wireless@vger.kernel.org>,
<phhuang@realtek.com>, <kevin_yang@realtek.com>
Subject: Re: [PATCH 1/2] rtw88: dump FW crash via devcoredump
Date: Tue, 22 Jun 2021 15:21:45 +0000 (UTC) [thread overview]
Message-ID: <20210622152145.747EEC4338A@smtp.codeaurora.org> (raw)
In-Reply-To: <20210528032901.12927-2-pkshih@realtek.com>
Ping-Ke Shih <pkshih@realtek.com> wrote:
> From: Zong-Zhe Yang <kevin_yang@realtek.com>
>
> Use device coredump framework instead of print_hex_dump to support
> FW crash dump. Pass data to the framework if preparing and dumping
> are successful. The framework will take the ownership of the data.
> The data will be freed after the framework determines its lifetime
> is over. A new coredump will not work if the previous one still
> exists.
>
> Signed-off-by: Zong-Zhe Yang <kevin_yang@realtek.com>
> Signed-off-by: Ping-Ke Shih <pkshih@realtek.com>
2 patches applied to wireless-drivers-next.git, thanks.
7b80f3e48c4b rtw88: dump FW crash via devcoredump
ae04f15b1a83 rtw88: refine unwanted h2c command
--
https://patchwork.kernel.org/project/linux-wireless/patch/20210528032901.12927-2-pkshih@realtek.com/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2021-06-22 15:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-28 3:28 [PATCH 0/2] rtw88: dump firmware log by devcoredump and refine unwanted H2C Ping-Ke Shih
2021-05-28 3:29 ` [PATCH 1/2] rtw88: dump FW crash via devcoredump Ping-Ke Shih
2021-06-22 15:21 ` Kalle Valo [this message]
2021-05-28 3:29 ` [PATCH 2/2] rtw88: refine unwanted h2c command Ping-Ke Shih
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=20210622152145.747EEC4338A@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=kevin_yang@realtek.com \
--cc=linux-wireless@vger.kernel.org \
--cc=phhuang@realtek.com \
--cc=pkshih@realtek.com \
--cc=tony0620emma@gmail.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).