netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhu Yi <yi.zhu@intel.com>
To: Simon Barber <simon@devicescape.com>
Cc: netdev@vger.kernel.org
Subject: RE: [PATCH 5/6] d80211: add IEEE 802.11e Direct Link Setup (DLS) support
Date: Mon, 18 Dec 2006 17:19:23 +0800	[thread overview]
Message-ID: <1166433563.10342.45.camel@debian.sh.intel.com> (raw)
In-Reply-To: <C86180A8C204554D8A3323D8F6B0A29F01A1A8B8@dhost002-46.dex002.intermedia.net>

On Thu, 2006-12-14 at 21:48 -0800, Simon Barber wrote:
> Again - this DLS management frame processing code should not be in the
> kernel - it should be in wpa_supplicant.
> 
> Only the frame processing code should be in the kernel.

OK. The DLS management process code needs the decision making from the
user. I agree to move them to userspace. But the frame sending code and
DLS data structure should be in the kernel.

Thanks,
-yi

      reply	other threads:[~2006-12-18  9:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-14  4:02 [PATCH 5/6] d80211: add IEEE 802.11e Direct Link Setup (DLS) support Zhu Yi
2006-12-15  5:48 ` Simon Barber
2006-12-18  9:19   ` Zhu Yi [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=1166433563.10342.45.camel@debian.sh.intel.com \
    --to=yi.zhu@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=simon@devicescape.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).