From: Zhu Yi <yi.zhu@intel.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Michael Wu <flamingice@sourmilk.net>,
linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
David Lamparter <lists@diac24.net>, Thomas Graf <tgraf@suug.ch>,
netdev <netdev@vger.kernel.org>
Subject: Re: wireless userspace MLME and generic netlink vs. multicast (was: Re: [Take 2] mac80211 IEEE802.11e/WMM code cleanup)
Date: Mon, 18 Jun 2007 10:08:47 +0800 [thread overview]
Message-ID: <1182132527.4092.90.camel@debian.sh.intel.com> (raw)
In-Reply-To: <1182081831.23681.29.camel@johannes.berg>
On Sun, 2007-06-17 at 14:03 +0200, Johannes Berg wrote:
> It sounds to me like you're proposing that wpa_supplicant is the only
> supported userspace MLME and that wpa_cli is the only way to configure
> it, basically. I sure hope that isn't so.
OK. This is the key of the discussion. Do we take wpa_supplicant the
only implementation of userspace MLME or even decision making (ie. DLS
config) daemon? If so, we don't need the API. Otherwise we'd better have
the API in the kernel because we cannot expect both userspace MLME
implentation A and B support the same API (via IPC) for configuration.
Thanks,
-yi
next prev parent reply other threads:[~2007-06-18 2:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070611085950.GA5540@mail.intel.com>
[not found] ` <200706161129.13782.flamingice@sourmilk.net>
[not found] ` <1182019869.9058.57.camel@johannes.berg>
[not found] ` <200706161516.16447.flamingice@sourmilk.net>
2007-06-17 12:03 ` wireless userspace MLME and generic netlink vs. multicast (was: Re: [Take 2] mac80211 IEEE802.11e/WMM code cleanup) Johannes Berg
2007-06-18 2:08 ` Zhu Yi [this message]
2007-06-18 8:46 ` Johannes Berg
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=1182132527.4092.90.camel@debian.sh.intel.com \
--to=yi.zhu@intel.com \
--cc=flamingice@sourmilk.net \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lists@diac24.net \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
/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).