K 10
svn:author
V 6
adrian
K 8
svn:date
V 27
2013-03-02T09:26:59.435840Z
K 7
svn:log
V 441
Revert the VAP TX task stuff and go back to direct dispatch.

Deferring the VAP TX side of things doesn't buy us anything.
The only thing is currently buys is serialising the AMPDU TX handling
in this path - but it doesn't at all serialise the AMPDU TX handling
from other paths (eg mesh TX.)

The current locking implementation still serialises the TX path correctly
for 802.11 sequence number handling and driver dispatch, so that's good.

END