From: Kalle Valo <kvalo@qca.qualcomm.com>
To: <ath10k@lists.infradead.org>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 0/3] ath10k: HTT stats
Date: Fri, 6 Sep 2013 12:43:17 +0300 [thread overview]
Message-ID: <87ioyei8ui.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20130903084302.26199.3538.stgit@localhost6.localdomain6> (Kalle Valo's message of "Tue, 03 Sep 2013 11:43:48 +0300")
Kalle Valo <kvalo@qca.qualcomm.com> writes:
> Adds trace events and a debugfs interface to enable HTT stats
> from firmware.
>
> ---
>
> Kalle Valo (3):
> ath10k: add trace event ath10k_htt_stats
> ath10k: implement ath10k_debug_start/stop()
> ath10k: add htt_stats_enable debugfs file
All three applied.
--
Kalle Valo
prev parent reply other threads:[~2013-09-06 9:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 8:43 [PATCH 0/3] ath10k: HTT stats Kalle Valo
2013-09-03 8:43 ` [PATCH 1/3] ath10k: add trace event ath10k_htt_stats Kalle Valo
2013-09-03 8:44 ` [PATCH 2/3] ath10k: implement ath10k_debug_start/stop() Kalle Valo
2013-09-03 8:44 ` [PATCH 3/3] ath10k: add htt_stats_enable debugfs file Kalle Valo
2013-09-06 9:43 ` 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=87ioyei8ui.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;
as well as URLs for NNTP newsgroup(s).