From: Sujith Manoharan <sujith@msujith.org>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: "ath10k\@lists.infradead.org" <ath10k@lists.infradead.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] ath10k: Block radar events when requested
Date: Mon, 17 Nov 2014 17:23:55 +0530 [thread overview]
Message-ID: <21609.57811.107846.718878@gargle.gargle.HOWL> (raw)
In-Reply-To: <CA+BoTQkpqVKVHFoXuTJtkTmFZA0XfU56nLRaVegWUr29z83_tQ@mail.gmail.com>
Michal Kazior wrote:
> The simulate_radar knob is meant to be used with
> dfs_block_radar_events being true in the first place so you can easily
> block real DFS events and inject fake ones for testing of DFS upper
> layers with ath10k.
>
> Your patch breaks this. Why would you want to do that?
Apparently, this knob is also being used to make sure that
radar detection doesn't happen when NOL is disabled.
I'll check if this test case is needed at all before
adding another knob to the existing pile...
Sujith
prev parent reply other threads:[~2014-11-17 11:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 7:29 [PATCH] ath10k: Block radar events when requested Sujith Manoharan
2014-11-17 11:32 ` Michal Kazior
2014-11-17 11:53 ` Sujith Manoharan [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=21609.57811.107846.718878@gargle.gargle.HOWL \
--to=sujith@msujith.org \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.kazior@tieto.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