Johannes Berg wrote: > Mesh also used (and needed to!) RX_QUEUED for the case where it actually > wanted the packet. I just wrote the code the other way around -- before > it was returning RX_QUEUED if wanted, now it short-cuts to > "RX_DROP_MONITOR" if unwanted. > > > Wouldn't this change mesh mode's existing behavior ? > > No, I don't think it does, in ieee80211_rx_h_mgmt() RX_CONTINUE and > RX_DROP_MONITOR are equivalent since that's the last possible thing to > happen with a (management) frame. Unless I'm misunderstanding you? Ok. I assumed that RX_CONTINUE was needed by mesh for some purpose. 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
