From: "Valo, Kalle" <kvalo@qca.qualcomm.com>
To: "Shajakhan, Mohammed Shafi (Mohammed Shafi)" <mohammed@qti.qualcomm.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
"mohammed@codeaurora.org" <mohammed@codeaurora.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 2/2] ath10k: Enable parsing per station rx duration for 10.4
Date: Wed, 16 Mar 2016 10:22:22 +0000 [thread overview]
Message-ID: <87d1qulo2r.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1458052250-2529-3-git-send-email-mohammed@qca.qualcomm.com> (Mohammed Shafi Shajakhan's message of "Tue, 15 Mar 2016 20:00:50 +0530")
Mohammed Shafi Shajakhan <mohammed@qti.qualcomm.com> writes:
> From: Mohammed Shafi Shajakhan <mohammed@qti.qualcomm.com>
>
> Rx duration support for per station is part of extended peer
> stats, enable provision to parse the same and provide backward
> compatibility based on the 'stats_id' event
>
> Signed-off-by: Mohammed Shafi Shajakhan <mohammed@qti.qualcomm.com>
After fixing patch 1 this doesn't compile either. Please fix and resend
both patches.
drivers/net/wireless/ath/ath10k/core.c: In function 'ath10k_core_start':
drivers/net/wireless/ath/ath10k/core.c:1787:3: error: implicit
declaration of function 'ath10k_peer_stats_enabled'
[-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors
--
Kalle Valo
next prev parent reply other threads:[~2016-03-16 10:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 14:30 [PATCH 0/2] Parsing per station rx duration for 10.4 Mohammed Shafi Shajakhan
2016-03-15 14:30 ` [PATCH 1/2] ath10k: Introduce Extended Resource Config support " Mohammed Shafi Shajakhan
2016-03-16 10:21 ` Valo, Kalle
2016-03-16 11:16 ` Mohammed Shafi Shajakhan
2016-03-15 14:30 ` [PATCH 2/2] ath10k: Enable parsing per station rx duration " Mohammed Shafi Shajakhan
2016-03-16 10:22 ` Valo, Kalle [this message]
2016-03-16 11:19 ` Mohammed Shafi Shajakhan
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=87d1qulo2r.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mohammed@codeaurora.org \
--cc=mohammed@qti.qualcomm.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;
as well as URLs for NNTP newsgroup(s).