From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
Cc: ath10k@lists.infradead.org
Subject: Re: [PATCH] ath10k Suppress 'failed to process fft' warning messages.
Date: Tue, 21 Jul 2015 15:04:36 +0300 [thread overview]
Message-ID: <87bnf5ogx7.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1437075444-6779-1-git-send-email-kevin@darbyshire-bryant.me.uk> (Kevin Darbyshire-Bryant's message of "Thu, 16 Jul 2015 20:37:24 +0100")
Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk> writes:
> When using DFS channels on Ath10k kernel log has warning message 'failed
> to process fft', typically when under medium/heavy traffic. Ticket
> https://dev.openwrt.org/ticket/19316 discusses and concludes messages
> are harmless. They do still contribute to log noise, so this patch
> enables them only in driver debug mode.
>
> Signed-off-by: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
Don't reference to a discussion somewhere else with a link, instead
summarise the discussion in the commit log.
And please change the title to: ath10k: suppress 'failed to process fft'
warning messages. Also please CC linux-wireless list as instructed here:
https://wireless.wiki.kernel.org/en/users/drivers/ath10k/sources#submitting_patches
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2015-07-21 12:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 19:37 [PATCH] ath10k Suppress 'failed to process fft' warning messages Kevin Darbyshire-Bryant
2015-07-21 12:04 ` Kalle Valo [this message]
2015-07-21 15:02 ` Kevin Darbyshire-Bryant
-- strict thread matches above, loose matches on Subject: below --
2015-07-21 14:50 [PATCH] ath10k: suppress " Kevin Darbyshire-Bryant
2015-07-29 8:25 ` 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=87bnf5ogx7.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=kevin@darbyshire-bryant.me.uk \
/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