From: Johannes Berg <johannes@sipsolutions.net>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: ath10k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v8 2/4] ath10k: provide firmware crash info via debugfs
Date: Sun, 24 Aug 2014 11:42:19 +0200 [thread overview]
Message-ID: <1408873339.24483.0.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <87egw8a8zg.fsf@kamboji.qca.qualcomm.com>
On Fri, 2014-08-22 at 17:34 +0300, Kalle Valo wrote:
> We really would have use for this, that's why I'm hesitant to wait more.
> Even having this from an "unofficial" location would be a big help. If
> it's ok for you, I would like to apply this once all review comments are
> addressed. But naturally if you think it's better to wait, I will do
> that.
No, I don't care what you do. I'm just saying I'm working on a
framework, so you might want to wait. If you don't, that's perfectly
fine with me.
johannes
next prev parent reply other threads:[~2014-08-24 9:42 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 [this message]
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 ` [PATCH v8 0/4] ath10k: firmware crash dump 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=1408873339.24483.0.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@qca.qualcomm.com \
--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;
as well as URLs for NNTP newsgroup(s).