From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Bartosz Markowski <bartosz.markowski@tieto.com>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH] ath10k: remove excessive rx msdu len check
Date: Thu, 13 Feb 2014 16:48:08 +0200 [thread overview]
Message-ID: <87y51f83x3.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1392104226-12096-1-git-send-email-bartosz.markowski@tieto.com> (Bartosz Markowski's message of "Tue, 11 Feb 2014 08:37:06 +0100")
Bartosz Markowski <bartosz.markowski@tieto.com> writes:
> This throw a lot of pointless warnings in case of DFS (radar
> detection) and PHYERR events from firmware, when firmware may
> actually insert more data, than we assume.
>
> Besides of being noisy this debug does not protect or check
> anything usefull currently. It was introduced long time ago
> while debugging aggregations. So just removing it.
>
> Signed-off-by: Bartosz Markowski <bartosz.markowski@tieto.com>
Thanks, applied.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2014-02-13 14:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-11 7:37 [PATCH] ath10k: remove excessive rx msdu len check Bartosz Markowski
2014-02-13 14:48 ` Kalle Valo [this message]
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=87y51f83x3.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=bartosz.markowski@tieto.com \
--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