summaryrefslogtreecommitdiffstats
path: root/Documentation/zh_CN/SubmittingDrivers
diff options
context:
space:
mode:
authorJohannes Berg <johannes@sipsolutions.net>2009-03-23 17:28:39 +0100
committerJohn W. Linville <linville@tuxdriver.com>2009-03-27 20:13:22 -0400
commitb1720231ca07dee3382980f3b25e6581bd2e54e9 (patch)
tree4258dec3d4774ee5968f181533c77766c8584b79 /Documentation/zh_CN/SubmittingDrivers
parent1870cd71e87da1a1afb904f2c84086f487a07135 (diff)
downloadop-kernel-dev-b1720231ca07dee3382980f3b25e6581bd2e54e9.zip
op-kernel-dev-b1720231ca07dee3382980f3b25e6581bd2e54e9.tar.gz
mac80211: unify and fix TX aggregation start
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@sipsolutions.net> Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'Documentation/zh_CN/SubmittingDrivers')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud