On Mon, 2011-01-31 at 11:04 -0800, Ben Greear wrote: > >> The set-channel-type logic will complain, and I imagine the interfaces > >> will bounce around and attempt to re-associate, but I think it can > >> get into the mixed state. > > > > I think we should try to avoid that. > > Ok. I haven't actually tested that case yet. It's possible > that we can't actually get in that case..but I haven't found > anything that prevents it while reading code. Assuming there is a problem, > what would be the preferred fix? Maybe force to NO_HT if an interface > tries to associate with HT40+/- mis-match? I think ieee80211_enable_ht() checks this? > Do you want me to repost this patch without the WARN_ON_ONCE > changes? For now, I think that'd be nicer. I suspect it doesn't actually matter since the above means we can't get into that situation. Still we may want WARN_ON_ONCE to prevent being flooded, but I guess it should be a separate patch? 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
