From: "John W. Linville" <linville@tuxdriver.com>
To: Chaoxing Lin <CLin@3eti.com>
Cc: "'Zefir Kurtisi'" <zefir.kurtisi@neratec.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [RFC] DFS userspace handler
Date: Wed, 9 Feb 2011 11:30:30 -0500 [thread overview]
Message-ID: <20110209163030.GD2494@tuxdriver.com> (raw)
In-Reply-To: <BD54DDEB2546894FAB0731EA7B0EDF8D0571DC34@RockMX01.rock.corp>
On Wed, Feb 09, 2011 at 04:09:08PM +0000, Chaoxing Lin wrote:
> I would vote for a dedidate DFS daemon.
>
> Straightforward name is better.
> Beginners would be hard to understand why WDS/Mesh/IBSS mode requires a hostapd daemon which intuitively means for AP mode..
Perhaps it can be in wpa_supplicant instead?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2011-02-09 16:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 12:01 [RFC] DFS userspace handler Zefir Kurtisi
2011-02-09 12:01 ` [PATCH 1/2] nl80211: interface update Zefir Kurtisi
2011-02-09 14:31 ` John W. Linville
2011-02-09 15:32 ` Zefir Kurtisi
2011-02-14 10:20 ` Johannes Berg
2011-02-14 15:54 ` Zefir Kurtisi
2011-02-09 12:01 ` [PATCH 2/2] ath9k: pulse detection Zefir Kurtisi
2011-02-09 15:15 ` Vasanth Thiagarajan
2011-02-09 15:30 ` Zefir Kurtisi
2011-02-09 12:01 ` [PATCH 1/3] hostapd: simple pattern detector Zefir Kurtisi
2011-02-09 12:01 ` [PATCH 2/3] hostapd: nl80211 interface Zefir Kurtisi
2011-02-09 12:01 ` [PATCH 3/3] hostapd: integrate DFS detection Zefir Kurtisi
2011-02-09 14:34 ` [RFC] DFS userspace handler John W. Linville
2011-02-09 15:35 ` Chaoxing Lin
2011-02-09 15:50 ` Zefir Kurtisi
2011-02-09 16:09 ` Chaoxing Lin
2011-02-09 16:30 ` John W. Linville [this message]
2011-02-09 17:09 ` Chaoxing Lin
2011-02-09 17:50 ` Jouni Malinen
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=20110209163030.GD2494@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=CLin@3eti.com \
--cc=linux-wireless@vger.kernel.org \
--cc=zefir.kurtisi@neratec.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).