From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH 0/4] ath10k: fix/cleanup fw stats
Date: Fri, 26 Sep 2014 14:06:42 +0300 [thread overview]
Message-ID: <871tqy63p9.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1411641230-18785-1-git-send-email-michal.kazior@tieto.com> (Michal Kazior's message of "Thu, 25 Sep 2014 12:33:46 +0200")
Michal Kazior <michal.kazior@tieto.com> writes:
> Hi,
>
> This cleans up and fixes fw stats aggregation.
>
>
> Michal Kazior (4):
> ath10k: split wmi stats parsing
> ath10k: rename fw_stats related stuff
> ath10k: request fw_stats once on open
> ath10k: fix fw stats processing
I didn't review these yet but I saw new warnings:
drivers/net/wireless/ath/ath10k/debug.c: In function 'ath10k_fw_stats_fill':
drivers/net/wireless/ath/ath10k/debug.c:540:5: warning: format '%lu' expects argument of type 'long unsigned int', but argument 5 has type 'size_t' [-Wformat]
drivers/net/wireless/ath/ath10k/wmi.c:1513: WARNING: else is not generally useful after a break or return
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2014-09-26 11:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 10:33 [PATCH 0/4] ath10k: fix/cleanup fw stats Michal Kazior
2014-09-25 10:33 ` [PATCH 1/4] ath10k: split wmi stats parsing Michal Kazior
2014-09-25 10:33 ` [PATCH 2/4] ath10k: rename fw_stats related stuff Michal Kazior
2014-09-25 10:33 ` [PATCH 3/4] ath10k: request fw_stats once on open Michal Kazior
2014-09-25 10:33 ` [PATCH 4/4] ath10k: fix fw stats processing Michal Kazior
2014-09-27 8:01 ` Kalle Valo
2014-09-29 7:16 ` Michal Kazior
2014-09-29 7:38 ` Kalle Valo
2014-09-26 11:06 ` Kalle Valo [this message]
2014-09-26 11:14 ` [PATCH 0/4] ath10k: fix/cleanup fw stats Michal Kazior
2014-09-26 14:14 ` Joe Perches
2014-09-29 11:32 ` 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=871tqy63p9.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.kazior@tieto.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