From: Kalle Valo <kvalo@codeaurora.org>
To: Govind Singh <govinds@codeaurora.org>
Cc: ath10k@lists.infradead.org, linux-wireless@vger.kernel.org,
Govind Singh <govinds@codeaurora.org>
Subject: Re: [PATCH 2/2] ath10k: Enable pktlog for WCN3990 target
Date: Tue, 4 Sep 2018 05:07:20 +0000 (UTC) [thread overview]
Message-ID: <20180904050720.8DDA3606AC@smtp.codeaurora.org> (raw)
In-Reply-To: <20180828043642.14890-3-govinds@codeaurora.org>
Govind Singh <govinds@codeaurora.org> wrote:
> WCN3990 target uses separate htc service for pktlog.
> Add pktlog service request and support for pktlog
> rx path handling.
>
> Testing:
> Tested on WCN3990 and QCA6174 HW.
> Tested FW: WLAN.HL.2.0-01192-QCAHLSWMTPLZ-1,
> WLAN.RM.4.4.1-00109-QCARMSWPZ-1
>
> Signed-off-by: Govind Singh <govinds@codeaurora.org>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
This introduced a new sparse warning:
drivers/net/wireless/ath/ath10k/htc.c:875:6: warning: symbol 'ath10k_htc_pktlog_svc_supported' was not declared. Should it be static?
I fixed this in the pending branch.
--
https://patchwork.kernel.org/patch/10577869/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2018-09-04 9:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-28 4:36 [PATCH 0/2] ath10k: Enable pktlog for WCN3990 chipset Govind Singh
2018-08-28 4:36 ` [PATCH 1/2] ath10k: Introduce CE_ATTR_POLL attribute for polling pipe Govind Singh
2018-09-06 15:55 ` Kalle Valo
2018-08-28 4:36 ` [PATCH 2/2] ath10k: Enable pktlog for WCN3990 target Govind Singh
2018-08-28 14:53 ` kbuild test robot
2018-08-28 14:53 ` [RFC PATCH] ath10k: ath10k_htc_pktlog_svc_supported() can be static kbuild test robot
2018-09-04 5:07 ` 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=20180904050720.8DDA3606AC@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=govinds@codeaurora.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).