Johannes Berg wrote: > Yes, that's true. However, we use the sta.ht_cap field more of a current > operating set database. For example, we also update it when the station > changes SMPS configuration. Also, we never keep it at just the station's > capabilities -- we always restrict it by our own TX capabilities (so if > for example we aren't 40 MHz capable, we already don't leave 40 MHz in). Ah, that's true. > Overall, I don't really see a problem with this. I suppose we could > rename the field to make that a bit clearer, but I see little value in > using some other struct or so? Yeah, the current approach seems reasonable enough. Thanks for clarifying. Sujith -- 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
