On Tue, 2010-09-21 at 09:42 -0700, Ben Greear wrote: > On 09/21/2010 09:30 AM, Johannes Berg wrote: > > On Tue, 2010-09-21 at 09:25 -0700, Ben Greear 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. johannes -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
