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: Thu, 20 Dec 2018 17:06:24 +0000 (UTC) [thread overview]
Message-ID: <20181220170624.5414060736@smtp.codeaurora.org> (raw)
In-Reply-To: <20181129042522.11767-1-govinds@codeaurora.org>
Govind Singh <govinds@codeaurora.org> wrote:
> During driver load below warn logs are printed in the console.
> Since driver may not implement all wmi events sent by fw and
> all of them are non-fatal, move this log to debug level to
> remove un-necessary warn message on console.
>
> [ 361.887230] ath10k_snoc a000000.wifi: Unknown eventid: 16393
> [ 361.907037] ath10k_snoc a000000.wifi: Unknown eventid: 237569
>
> 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.
bd085be6ba95 ath10k: move non-fatal warn logs to dbg level
--
https://patchwork.kernel.org/patch/10703901/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2018-12-20 17:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 4:25 [PATCH] ath10k: Move non-fatal warn logs to dbg level Govind Singh
2018-11-29 4:25 ` Govind Singh
2018-11-30 20:59 ` Brian Norris
2018-11-30 20:59 ` Brian Norris
2018-12-20 16:40 ` Kalle Valo
2018-12-20 16:40 ` Kalle Valo
2018-12-20 17:43 ` Brian Norris
2018-12-20 17:43 ` Brian Norris
2018-12-20 17:06 ` Kalle Valo
2018-12-20 17:06 ` Kalle Valo [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-11-25 13:10 [PATCH] ath10k: move " Govind Singh
2019-11-25 13:10 Govind Singh
2019-11-27 15:48 ` Kalle Valo
2019-11-27 15:48 ` 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=20181220170624.5414060736@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.