From: Johannes Berg <johannes@sipsolutions.net>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] RFC: v3: Support multiple STA on same AP with ath9k
Date: Fri, 10 Sep 2010 23:27:01 +0200 [thread overview]
Message-ID: <c358124867aecc372764a1a7c56a3890@localhost> (raw)
In-Reply-To: <4C8AA1C5.8080906@candelatech.com>
On Fri, 10 Sep 2010 14:23:17 -0700, Ben Greear <greearb@candelatech.com>
wrote:
> As for counting, as far as I can tell, ath9k doesn't keep a list of
> interfaces, but rather calls those iterator methods when it wants to
> know them, so one way or another I need to call back into mac80211.
But it can just call the atomic iterator with a callback that
keeps the count.
> I'll break the patches apart for the next posting.
>
> Did you get a chance to think more about this part of the patch?
No, I didn't, and since I'm at the wireless summit now it
seems unlikely that I'll get to it before I get/go back
home on Monday (US time morning).
johannes
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>
Cc: <linux-wireless@vger.kernel.org>,
"ath9k-devel@lists.ath9k.org" <ath9k-devel@venema.h4ckr.net>
Subject: Re: RFC: v3: Support multiple STA on same AP with ath9k
Date: Fri, 10 Sep 2010 23:27:01 +0200 [thread overview]
Message-ID: <c358124867aecc372764a1a7c56a3890@localhost> (raw)
In-Reply-To: <4C8AA1C5.8080906@candelatech.com>
On Fri, 10 Sep 2010 14:23:17 -0700, Ben Greear <greearb@candelatech.com>
wrote:
> As for counting, as far as I can tell, ath9k doesn't keep a list of
> interfaces, but rather calls those iterator methods when it wants to
> know them, so one way or another I need to call back into mac80211.
But it can just call the atomic iterator with a callback that
keeps the count.
> I'll break the patches apart for the next posting.
>
> Did you get a chance to think more about this part of the patch?
No, I didn't, and since I'm at the wireless summit now it
seems unlikely that I'll get to it before I get/go back
home on Monday (US time morning).
johannes
next prev parent reply other threads:[~2010-09-10 21:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-10 20:07 [ath9k-devel] RFC: v3: Support multiple STA on same AP with ath9k Ben Greear
2010-09-10 20:07 ` Ben Greear
2010-09-10 21:12 ` [ath9k-devel] " Johannes Berg
2010-09-10 21:12 ` Johannes Berg
2010-09-10 21:23 ` [ath9k-devel] " Ben Greear
2010-09-10 21:23 ` Ben Greear
2010-09-10 21:27 ` Johannes Berg [this message]
2010-09-10 21:27 ` Johannes Berg
2010-09-13 12:14 ` [ath9k-devel] " Vasanthakumar Thiagarajan
2010-09-13 12:14 ` Vasanthakumar Thiagarajan
2010-09-13 14:36 ` [ath9k-devel] " Ben Greear
2010-09-13 14:36 ` Ben Greear
2010-09-13 19:23 ` [ath9k-devel] " Ben Greear
2010-09-13 19:23 ` Ben Greear
2010-09-14 13:46 ` [ath9k-devel] " Vasanthakumar Thiagarajan
2010-09-14 13:46 ` Vasanthakumar Thiagarajan
2010-09-14 14:39 ` [ath9k-devel] " Ben Greear
2010-09-14 14:39 ` Ben Greear
2010-09-14 14:44 ` [ath9k-devel] " Vasanthakumar Thiagarajan
2010-09-14 14:44 ` Vasanthakumar Thiagarajan
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=c358124867aecc372764a1a7c56a3890@localhost \
--to=johannes@sipsolutions.net \
--cc=ath9k-devel@lists.ath9k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.