On Wed, 2010-03-17 at 10:26 +0100, Stanislaw Gruszka wrote: > > Sorry ... I had given this some thought and then got distracted ... > > still had it unread but no time to reply. What I finally realised is > > that we set the information per queue, and even the userspace API is > > built that way, so we really need to have a separate configuration to > > enable/disable QoS. Maybe a BSS config flag would be appropriate? > > Maybe in -next but not in -stable since drivers in ieee80211_ops->config > and ieee80211_ops->bss_info_chnged do some additional work not looking at > changed variable. So my plan is put change I proposed in stable and > further optimize it in -next, ok? I really don't think it should work that way. I'd like to see the patch for the current kernels including 2.6.34 first, and then we can decide how to backport it. FWIW, I don't think drivers should be having trouble with a new flag there. 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
