All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [mac80211] mac80211:  Support multiple VIFS per AP in debugfs.
Date: Wed, 22 Sep 2010 09:59:41 -0700	[thread overview]
Message-ID: <4C9A35FD.8060201@candelatech.com> (raw)
In-Reply-To: <1285091341.12764.7.camel@jlt3.sipsolutions.net>

On 09/21/2010 10:49 AM, Johannes Berg wrote:
> On Tue, 2010-09-21 at 19:03 +0200, Johannes Berg wrote:
>
>>>>>> -	snprintf(mac, sizeof(mac), "%pM", sta->sta.addr);
>>>>>> +	snprintf(mac, sizeof(mac), "%pM-%s",
>>>>>> +		 sta->sta.addr, sta->sdata->name);
>>>>>>
>>>>>>     	/*
>>>>>>     	 * This might fail due to a race condition:
>>>>>
>>>>> I got to thinking:  Is there any reason to put the sta.addr in there?
>>>>>
>>>>> Maybe just use sta->sdata->name?  Seems it might be easier for
>>>>> scripts to deal with?
>>>>
>>>> APs have many STAs
>>>
>>> So, when in STA mode, sta_info are related to local VIFs, but
>>> in AP mode, they represent the remote wireless devices, with sdata pointing
>>> to the local AP interface?
>>
>> No, there's a sta_info for each peer, which in STA mode is only the AP.
>
> maybe the stations should be moved from phy0/stations/ to
> phy0/wlan0/stations/ instead?

It doesn't matter either way to me, but I'd like to get one or another
patch upstream.

If you want me to change it to put stations under netdev:wlan0/ instead,
please just let me know.

Thanks,
Ben

>
> johannes


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


  parent reply	other threads:[~2010-09-22 16:59 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-21 12:15 [mac80211] mac80211: Support multiple VIFS per AP in debugfs greearb
2010-09-21 16:25 ` Ben Greear
2010-09-21 16:30   ` Johannes Berg
2010-09-21 16:42     ` Ben Greear
2010-09-21 17:03       ` Johannes Berg
2010-09-21 17:49         ` Johannes Berg
2010-09-21 18:02           ` Ben Greear
2010-09-22 16:59           ` Ben Greear [this message]
2010-09-22 17:01             ` Johannes Berg
2010-09-22 17:34               ` Ben Greear
2010-09-22 18:31                 ` Johannes Berg
2010-09-22 18:48                   ` John W. Linville
2010-09-22 19:45                     ` Ben Greear
2010-09-23  8:30                       ` Johannes Berg
2010-09-23 13:12                         ` Ben Greear
  -- strict thread matches above, loose matches on Subject: below --
2010-09-23  3:29 greearb
2010-09-23  8:36 ` Johannes Berg
2010-10-16 19:00   ` Christian Lamparter
2010-10-18 20:05     ` Ben Greear
     [not found]     ` <4CDAF182.4030409@candelatech.com>
2010-11-10 20:01       ` Christian Lamparter
2010-09-21  4:21 greearb
2010-09-21  6:48 ` Johannes Berg
2010-09-21 12:04   ` Ben Greear

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=4C9A35FD.8060201@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=johannes@sipsolutions.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 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.