From: Ben Greear <greearb@candelatech.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ath9k-devel@lists.ath9k.org" <ath9k-devel@venema.h4ckr.net>
Subject: Re: RFC: v2: Support multiple STA on same AP with ath9k
Date: Fri, 10 Sep 2010 12:51:44 -0700 [thread overview]
Message-ID: <4C8A8C50.30902@candelatech.com> (raw)
In-Reply-To: <4C8A8B96.5050409@candelatech.com>
On 09/10/2010 12:48 PM, Ben Greear wrote:
> The attached patch lets mac80111 create multiple STA on the same
> AP, and the changes to ath9k let it function properly, at least for
> un-encrypted traffic. WPA does not work..no idea why yet.
>
> It also consolidates some of the util.c iterator logic in
> mac80211.
>
> Please let me know if this is moving in the right direction.
Ummm, the second I hit send I noticed my consolidation of the helper
logic broke things because I'm always using the _rcu variant of
the for loop...will fix that.
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2010-09-10 19:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-10 19:48 RFC: v2: Support multiple STA on same AP with ath9k Ben Greear
2010-09-10 19:51 ` Ben Greear [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=4C8A8C50.30902@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath9k-devel@venema.h4ckr.net \
--cc=linux-wireless@vger.kernel.org \
/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).