Broadcast mac address check is performed on an empty buffer pointer
before it is filled. Use the input frame pointer instead.
CRs-Fixed: 2191063
Change-Id: Ie02dcf05da70d52a0f3532b8d5647a7e8e0bcfe8
In a noisy enviornment setkey confirmation in SME queue
is not getting processed due to multiple beacons/probes
getting processed in PE queue which is of higher priority
than SME queue.
Instead of posting a message to SME queue, setkey confirmation
will run to completion using sme callback mechanism.
Change-Id: Ibe536dad13731e7086c5e0a9ed2a19c11f6e9193
CRs-Fixed: 2233210
In lim_oper_chan_change_confirm_tx_complete_cnf, need free frame buf
alloced in lim_p2p_oper_chan_change_confirm_action_frame, or buffer is
leaked.
Change-Id: Ic479427282742fb4fbbe28ab1acdf91e0a511340
CRs-Fixed: 2238603
HE Tx beamforming config parameter setting fails due to incorrect
value range. Correct the HE Tx beamforming config parameter values
Change-Id: Idb0ada45417467122bd7473cca07d15cf54fd3cc
CRs-Fixed: 2244247
Fix tTxrateinfoflags as per linux coding guidelines, this will later
help move the struct to qcacmn.
Change-Id: I1911d25594aaecc7c166cf36b79111b61e6de457
CRs-Fixed: 2244834
The obss active dwell time does not match with OBSS IE in association
response, it is a mistake to assign passive dwell time of OBSS IE to
active dwell time, and the passive dwell time value is from ini, not
updated to OBSS IE value.
Assign OBSS IE passive dwell time to passive dwell time parameter.
Change-Id: I5e7945353d00f0411ef3d92534c3f170dec440a5
CRs-Fixed: 2239670
Address the following issues in the core/mac folder:
CHECK: 'absense' may be misspelled - perhaps 'absence'?
CHECK: 'accquired' may be misspelled - perhaps 'acquired'?
CHECK: 'acknowledgement' may be misspelled - perhaps 'acknowledgment'?
CHECK: 'arbitary' may be misspelled - perhaps 'arbitrary'?
CHECK: 'automaticly' may be misspelled - perhaps 'automatically'?
CHECK: 'calulate' may be misspelled - perhaps 'calculate'?
CHECK: 'couter' may be misspelled - perhaps 'counter'?
CHECK: 'defferred' may be misspelled - perhaps 'deferred'?
CHECK: 'Defintions' may be misspelled - perhaps 'Definitions'?
CHECK: 'dependant' may be misspelled - perhaps 'dependent'?
CHECK: 'dosen' may be misspelled - perhaps 'doesn'?
CHECK: 'endianess' may be misspelled - perhaps 'endianness'?
CHECK: 'explicitely' may be misspelled - perhaps 'explicitly'?
CHECK: 'fimware' may be misspelled - perhaps 'firmware'?
CHECK: 'fucntion' may be misspelled - perhaps 'function'?
CHECK: 'Funtion' may be misspelled - perhaps 'Function'?
CHECK: 'immediatly' may be misspelled - perhaps 'immediately'?
CHECK: 'implemetation' may be misspelled - perhaps 'implementation'?
CHECK: 'Intialize' may be misspelled - perhaps 'Initialize'?
CHECK: 'lengh' may be misspelled - perhaps 'length'?
CHECK: 'managment' may be misspelled - perhaps 'management'?
CHECK: 'Managment' may be misspelled - perhaps 'Management'?
CHECK: 'messsages' may be misspelled - perhaps 'messages'?
CHECK: 'Notifed' may be misspelled - perhaps 'Notified'?
CHECK: 'parametes' may be misspelled - perhaps 'parameters'?
CHECK: 'Paramters' may be misspelled - perhaps 'Parameters'?
CHECK: 'processsing' may be misspelled - perhaps 'processing'?
CHECK: 'receving' may be misspelled - perhaps 'receiving'?
CHECK: 'Recieved' may be misspelled - perhaps 'Received'?
CHECK: 'reponse' may be misspelled - perhaps 'response'?
CHECK: 'reseting' may be misspelled - perhaps 'resetting'?
Change-Id: Id58b5bf38fe88007c88cbda62a1fc43c0f1b3a37
CRs-Fixed: 2241942
