From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Peter Oh <poh@qca.qualcomm.com>
Cc: <ath10k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 1/3] ath: Introduce chirp parameter used by DFS
Date: Thu, 5 Mar 2015 15:56:20 +0200 [thread overview]
Message-ID: <87k2yv4kfv.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1423775825-19498-1-git-send-email-poh@qca.qualcomm.com> (Peter Oh's message of "Thu, 12 Feb 2015 13:17:03 -0800")
Peter Oh <poh@qca.qualcomm.com> writes:
> Some of radar types such as FCC radar type 5 require
> to look up chirp in pulse to detect genuine radar and
> it will prevent DFS channels from false radar detection.
>
> Signed-off-by: Peter Oh <poh@qca.qualcomm.com>
Thanks, all three patches applied.
--
Kalle Valo
prev parent reply other threads:[~2015-03-05 13:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 21:17 [PATCH 1/3] ath: Introduce chirp parameter used by DFS Peter Oh
2015-02-12 21:17 ` [PATCH 2/3] ath10k: Update chirp value in pulse event Peter Oh
2015-02-12 21:17 ` [PATCH 3/3] ath: Enhance radar detection by looking up chirp Peter Oh
2015-02-12 21:28 ` [PATCH 1/3] ath: Introduce chirp parameter used by DFS Peter Oh
2015-03-05 13:56 ` 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=87k2yv4kfv.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=poh@qca.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).