On Wed, 18 Nov 2009, Johannes Berg wrote: > > Linus pointed out that del_timer_sync() isn't actually needed if we make > the timer able to deal with no longer being needed when it gets queued > _while_ we're in the locked section that also deletes it. For that the > timer function only needs to check the HT_ADDBA_RECEIVED_MSK bit as well > as the HT_ADDBA_REQUESTED_MSK bit, only if the former is clear should it > do anything. Ok, this looks sane. It's not really worth me Acking it, since I don't actually know the code or the hardware, so I can't really judge whether this is in any way a good thing. But from a "design patterns" standpoint it no longer triggers my WTF reaction. It's just bound to be more robust to have the timer just check the state of things itself rather than depend on some (complex and almost inevitably racy) "timer is only enabled IFF certain-state-is-true" rule. Linus -- 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
