From: Kalle Valo <kvalo@qca.qualcomm.com>
To: ath10k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v8 0/4] ath10k: firmware crash dump
Date: Mon, 25 Aug 2014 11:25:33 +0300 [thread overview]
Message-ID: <877g1x6kn6.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20140821124705.27159.67898.stgit@potku.adurom.net> (Kalle Valo's message of "Thu, 21 Aug 2014 15:48:50 +0300")
Kalle Valo <kvalo@qca.qualcomm.com> writes:
> And yet another version of firmware crash dumps. Now I dropped all dumps except
> firmware registers and tested all the features myself.
[...]
> Ben Greear (1):
> ath10k: provide firmware crash info via debugfs
>
> Kalle Valo (3):
> ath10k: add ath10k_pci_diag_* helpers
> ath10k: rename ath10k_pci_hif_dump_area() to ath10k_pci_fw_crashed_dump()
> ath10k: print more driver info when firmware crashes
Finally applied :)
I also applied the small diff to patch 2 to remove the unneeded use of
mutex in ath10k_fw_crash_dump_open().
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2014-08-25 8:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 12:48 [PATCH v8 0/4] ath10k: firmware crash dump Kalle Valo
2014-08-21 12:49 ` [PATCH v8 1/4] ath10k: add ath10k_pci_diag_* helpers Kalle Valo
2014-08-21 12:49 ` [PATCH v8 2/4] ath10k: provide firmware crash info via debugfs Kalle Valo
2014-08-21 13:10 ` Johannes Berg
2014-08-21 14:40 ` Kalle Valo
2014-08-22 1:19 ` Johannes Berg
2014-08-22 14:34 ` Kalle Valo
2014-08-24 9:42 ` Johannes Berg
2014-08-22 6:49 ` Michal Kazior
2014-08-25 6:28 ` Kalle Valo
2014-08-21 12:49 ` [PATCH v8 3/4] ath10k: rename ath10k_pci_hif_dump_area() to ath10k_pci_fw_crashed_dump() Kalle Valo
2014-08-21 12:49 ` [PATCH v8 4/4] ath10k: print more driver info when firmware crashes Kalle Valo
2014-08-25 8:25 ` Kalle Valo [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=877g1x6kn6.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox