From: Ryan Hsu <ryanhsu@qti.qualcomm.com>
To: Gabriel C <nix.or.die@gmail.com>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: ath10k_htt_rx_amsdu_allowed() noise
Date: Tue, 18 Jul 2017 07:14:19 +0000 [thread overview]
Message-ID: <79f47b0b-eb71-db71-2700-e30b01b11c76@qca.qualcomm.com> (raw)
In-Reply-To: <edbe270b-ba70-b844-f814-53d04d07d253@gmail.com>
On 07/16/2017 03:56 PM, Gabriel C wrote:
>
> Can ath10k_warn() be ath10k_dbg() there ? Maybe this ?
>
Looks good to me.
>
> From d4138d936635ca7b69ed7f7b0cda4914f0f07917 Mon Sep 17 00:00:00 2001
> From: Gabriel Craciunescu <nix.or.die@gmail.com>
> Date: Mon, 17 Jul 2017 00:45:29 +0200
> Subject: [PATCH] ath10k_htt_rx_amsdu_allowed(): change ath10k_warn() to th10k_dbg()
>
> Signed-off-by: Gabriel Craciunescu <nix.or.die@gmail.com>
> ---
> drivers/net/wireless/ath/ath10k/htt_rx.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/wireless/ath/ath10k/htt_rx.c b/drivers/net/wireless/ath/ath10k/htt_rx.c
> index 398dda978d6e..ad0306cd6ee1 100644
> --- a/drivers/net/wireless/ath/ath10k/htt_rx.c
> +++ b/drivers/net/wireless/ath/ath10k/htt_rx.c
> @@ -1514,7 +1514,7 @@ static bool ath10k_htt_rx_amsdu_allowed(struct ath10k *ar,
> */
>
> if (!rx_status->freq) {
> - ath10k_warn(ar, "no channel configured; ignoriframe(s)!\n");
> + ath10k_dbg(ar, ATH10K_DBG_HTT, "no channel configured, ignoring frame(s)!\n");
> return false;
> }
>
Can you send this as patch for reviewing, please?
--
Ryan Hsu
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2017-07-18 7:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-16 22:56 ath10k_htt_rx_amsdu_allowed() noise Gabriel C
2017-07-18 7:14 ` Ryan Hsu [this message]
2017-07-19 15:00 ` Gabriel C
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=79f47b0b-eb71-db71-2700-e30b01b11c76@qca.qualcomm.com \
--to=ryanhsu@qti.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nix.or.die@gmail.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