From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Gabriel C <nix.or.die@gmail.com>
Cc: <ath10k@lists.infradead.org>, <ryanhsu@qti.qualcomm.com>,
<joe@perches.com>, <linux-wireless@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
Gabriel Craciunescu <nix.or.die@gmail.com>
Subject: Re: [v3] ath10k: ath10k_htt_rx_amsdu_allowed() use ath10k_dbg()
Date: Tue, 8 Aug 2017 13:06:11 +0200 [thread overview]
Message-ID: <b458726452224508b342d1ab932e1fa2@euamsexm01a.eu.qualcomm.com> (raw)
In-Reply-To: <20170719191955.11518-1-nix.or.die@gmail.com>
Gabriel C <nix.or.die@gmail.com> wrote:
> Each time we get disconnected from AP we get flooded with messages like:
>
> ...
> ath10k_pci 0000:03:00.0: no channel configured; ignoring frame(s)!
> <until ratelimit kicks in>
> ath10k_warn: 155 callbacks suppressed
> ...
>
> Use ath10k_dbg() here too.
>
> Signed-off-by: Gabriel Craciunescu <nix.or.die@gmail.com>
> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
Patch applied to ath-next branch of ath.git, thanks.
984eb9053280 ath10k: ath10k_htt_rx_amsdu_allowed() use ath10k_dbg()
--
https://patchwork.kernel.org/patch/9853129/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Gabriel C <nix.or.die@gmail.com>
Cc: ryanhsu@qti.qualcomm.com, netdev@vger.kernel.org,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
ath10k@lists.infradead.org, joe@perches.com
Subject: Re: [v3] ath10k: ath10k_htt_rx_amsdu_allowed() use ath10k_dbg()
Date: Tue, 8 Aug 2017 13:06:11 +0200 [thread overview]
Message-ID: <b458726452224508b342d1ab932e1fa2@euamsexm01a.eu.qualcomm.com> (raw)
In-Reply-To: <20170719191955.11518-1-nix.or.die@gmail.com>
Gabriel C <nix.or.die@gmail.com> wrote:
> Each time we get disconnected from AP we get flooded with messages like:
>
> ...
> ath10k_pci 0000:03:00.0: no channel configured; ignoring frame(s)!
> <until ratelimit kicks in>
> ath10k_warn: 155 callbacks suppressed
> ...
>
> Use ath10k_dbg() here too.
>
> Signed-off-by: Gabriel Craciunescu <nix.or.die@gmail.com>
> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
Patch applied to ath-next branch of ath.git, thanks.
984eb9053280 ath10k: ath10k_htt_rx_amsdu_allowed() use ath10k_dbg()
--
https://patchwork.kernel.org/patch/9853129/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2017-08-08 11:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 15:37 [PATCH] ath10k_htt_rx_amsdu_allowed(): use ath10k_dbg() Gabriel C
2017-07-19 15:37 ` Gabriel C
2017-07-19 16:26 ` Joe Perches
2017-07-19 16:26 ` Joe Perches
2017-07-19 18:12 ` Gabriel C
2017-07-19 18:12 ` Gabriel C
2017-07-19 18:24 ` Gabriel Craciunescu
2017-07-19 18:24 ` Gabriel Craciunescu
2017-07-19 18:41 ` Ryan Hsu
2017-07-19 18:41 ` Ryan Hsu
2017-07-19 18:41 ` Ryan Hsu
2017-07-19 19:19 ` [PATCH v3] ath10k: ath10k_htt_rx_amsdu_allowed() " Gabriel Craciunescu
2017-07-19 19:19 ` Gabriel Craciunescu
2017-08-08 11:06 ` Kalle Valo [this message]
2017-08-08 11:06 ` [v3] " 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=b458726452224508b342d1ab932e1fa2@euamsexm01a.eu.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nix.or.die@gmail.com \
--cc=ryanhsu@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 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.