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] ath10k: move non-fatal warn logs to dbg level
Date: Wed, 27 Nov 2019 15:48:30 +0000 [thread overview]
Message-ID: <0101016ead8cb636-991010d3-6f67-49b4-8541-671290d350d1-000000@us-west-2.amazonses.com> (raw)
In-Reply-To: <0101016ea2aee542-7e69e860-2ad6-4897-959f-e934f1a459bb-000000@us-west-2.amazonses.com>
Govind Singh <govinds@codeaurora.org> wrote:
> During driver load below warn logs are printed in the console if
> firmware doesn't support some optional HTC services, ex:pktlog.
> It is likely some older fw version may not support PKTLOG HTC
> service as legacy fw uses HTC DATA service for pktlog.
> Move this log to debug level to remove un-necessary warn message
> on console.
>
> htc.c:803: ath10k_warn(ar, "unsupported HTC service id: %d\n",
> htc.c:881: ath10k_warn(ar, "unsupported HTC service id: %d\n",
>
> Signed-off-by: Govind Singh <govinds@codeaurora.org>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Patch applied to ath-next branch of ath.git, thanks.
ef39ac1b0d9f ath10k: move non-fatal warn logs to dbg level
--
https://patchwork.kernel.org/patch/11260371/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2019-11-27 15:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 13:10 [PATCH] ath10k: move non-fatal warn logs to dbg level Govind Singh
2019-11-27 15:48 ` Kalle Valo [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-11-29 4:25 [PATCH] ath10k: Move " Govind Singh
2018-11-30 20:59 ` Brian Norris
2018-12-20 16:40 ` Kalle Valo
2018-12-20 17:43 ` Brian Norris
2018-12-20 17:06 ` 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=0101016ead8cb636-991010d3-6f67-49b4-8541-671290d350d1-000000@us-west-2.amazonses.com \
--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).