Re: [ath9k-devel] [RFC/RFT 0/3] ath10k: fix beacon loss handling

2013-05-09 Thread Kalle Valo
Bartosz Markowski bartosz.markow...@tieto.com writes: Kalle, could you please submit/review these? I will not commit any patches which have either RFC or RFT tag. And I also review them in lower priority. So if you want me to commit something I recommend to use only PATCH. -- Kalle Valo

Re: [ath9k-devel] [RFC/RFT 0/3] ath10k: fix beacon loss handling

2013-05-09 Thread Bartosz Markowski
Michal, could you please address Kalle's comments. From me ACK for the series (tested OK) Bartosz On 9 May 2013 12:33, Kalle Valo kv...@qca.qualcomm.com wrote: Bartosz Markowski bartosz.markow...@tieto.com writes: Kalle, could you please submit/review these? I will not commit any patches

Re: [ath9k-devel] [RFC/RFT 0/3] ath10k: fix beacon loss handling

2013-05-08 Thread Bartosz Markowski
ACK Kalle, could you please submit/review these? Fixes quite serious problem. Bartosz On 6 May 2013 16:03, Michal Kazior michal.kaz...@tieto.com wrote: FW is lying about tx status. First two patches do a little cleanup. The last one fixes beacon loss handling. This can be considered a

[ath9k-devel] [RFC/RFT 0/3] ath10k: fix beacon loss handling

2013-05-06 Thread Michal Kazior
FW is lying about tx status. First two patches do a little cleanup. The last one fixes beacon loss handling. This can be considered a workaround depending on what original FW design called for. Michal Kazior (3): ath10k: report mgmt tx retry status as no_ack ath10k: cleanup tx completion