From: Kalle Valo <kvalo@codeaurora.org>
To: Wen Gong <wgong@codeaurora.org>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH v4 2/2] ath10k: add fw coredump for sdio when firmware assert
Date: Wed, 19 Aug 2020 19:00:50 +0300 [thread overview]
Message-ID: <87tuwyiq19.fsf@codeaurora.org> (raw)
In-Reply-To: <103b604e367a150850d4e8fe179c727f@codeaurora.org> (Wen Gong's message of "Tue, 18 Aug 2020 17:23:05 +0800")
Wen Gong <wgong@codeaurora.org> writes:
> On 2020-08-15 00:36, Kalle Valo wrote:
>> Wen Gong <wgong@codeaurora.org> writes:
>>
>> I did some changes in the pending branch, please check:
>>
> I compared this patch with patch in pending branch, it is OK for me.
Great, thanks for testing.
I also did some changes to the commit log and added an example output of
a firmware crash.
> [ 1378.680788] ath10k_sdio mmc1:0001:1: check fw reg : 400
But I could not find this message anywhere in upstream ath10k so I
assumed it's from an out-of-tree patch and removed it from the example.
--
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@codeaurora.org>
To: Wen Gong <wgong@codeaurora.org>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH v4 2/2] ath10k: add fw coredump for sdio when firmware assert
Date: Wed, 19 Aug 2020 19:00:50 +0300 [thread overview]
Message-ID: <87tuwyiq19.fsf@codeaurora.org> (raw)
In-Reply-To: <103b604e367a150850d4e8fe179c727f@codeaurora.org> (Wen Gong's message of "Tue, 18 Aug 2020 17:23:05 +0800")
Wen Gong <wgong@codeaurora.org> writes:
> On 2020-08-15 00:36, Kalle Valo wrote:
>> Wen Gong <wgong@codeaurora.org> writes:
>>
>> I did some changes in the pending branch, please check:
>>
> I compared this patch with patch in pending branch, it is OK for me.
Great, thanks for testing.
I also did some changes to the commit log and added an example output of
a firmware crash.
> [ 1378.680788] ath10k_sdio mmc1:0001:1: check fw reg : 400
But I could not find this message anywhere in upstream ath10k so I
assumed it's from an out-of-tree patch and removed it from the example.
--
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2020-08-19 16:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 7:27 [PATCH v4 0/2] add fw coredump for sdio when firmware assert Wen Gong
2019-09-24 7:27 ` Wen Gong
2019-09-24 7:27 ` [PATCH v4 1/2] ath10k: add bus type for each layout of coredump Wen Gong
2019-09-24 7:27 ` Wen Gong
2020-08-19 17:36 ` Kalle Valo
2020-08-19 17:36 ` Kalle Valo
2019-09-24 7:27 ` [PATCH v4 2/2] ath10k: add fw coredump for sdio when firmware assert Wen Gong
2019-09-24 7:27 ` Wen Gong
2020-08-14 16:36 ` Kalle Valo
2020-08-14 16:36 ` Kalle Valo
2020-08-18 9:23 ` Wen Gong
2020-08-18 9:23 ` Wen Gong
2020-08-19 16:00 ` Kalle Valo [this message]
2020-08-19 16:00 ` Kalle Valo
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=87tuwyiq19.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=wgong@codeaurora.org \
/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.