On Fri, Mar 27, 2009 at 7:27 PM, Luis R. Rodriguez <mcgrof@xxxxxxxxxxxxxxxxxxxxxx> wrote: > On Mon, Mar 23, 2009 at 05:28:39PM +0100, Johannes Berg wrote: >> When TX aggregation becomes operational, we do a number of steps: >> 1) print a debug message >> 2) wake the virtual queue >> 3) notify the driver >> >> Unfortunately, 1) and 3) are only done if the driver is first to >> reply to the aggregation request, it is, however, possible that the >> remote station replies before the driver! Thus, unify the code for >> this and call the new function ieee80211_agg_tx_operational in both >> places where TX aggregation can become operational. >> >> Additionally, rename the driver notification from >> IEEE80211_AMPDU_TX_RESUME to IEEE80211_AMPDU_TX_OPERATIONAL. >> >> Signed-off-by: Johannes Berg <johannes@xxxxxxxxxxxxxxxx> > > Nice catch man! > > Reviewed-by: Luis R. Rodriguez <lrodriguez@xxxxxxxxxxx> Hm, maybe also a backported version could go to stable? Perhaps we can trigger a panic on a UP box? Luis -- 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
