Re: [RESEND PATCH 15/16] wcn36xx: don't pad beacons for mesh

2016-03-29 Thread Bjorn Andersson
On Tue 29 Mar 14:41 PDT 2016, Bjorn Andersson wrote: > From: Jason Mobarak > > Patch "wcn36xx: Pad TIM PVM if needed" has caused a regression in mesh > beaconing. The field tim_off is always 0 for mesh mode, and thus > pvm_len (referring to the TIM length field) and pad are both incorrectly > c

[RESEND PATCH 15/16] wcn36xx: don't pad beacons for mesh

2016-03-29 Thread Bjorn Andersson
From: Jason Mobarak Patch "wcn36xx: Pad TIM PVM if needed" has caused a regression in mesh beaconing. The field tim_off is always 0 for mesh mode, and thus pvm_len (referring to the TIM length field) and pad are both incorrectly calculated. Thus, msg_body.beacon_length is incorrectly calculated

Re: [PATCH 15/16] wcn36xx: don't pad beacons for mesh

2016-03-29 Thread Sergei Shtylyov
Hello. On 3/29/2016 9:06 AM, Bjorn Andersson wrote: From: Jason Mobarak Patch "wcn36xx: Pad TIM PVM if needed" has caused a regression in mesh scripts/checkpatch.pl now enforces the specific commit citing format, i.e. <12-digit SHA1> (""). beaconing. The field tim_off is always 0 fo

[PATCH 15/16] wcn36xx: don't pad beacons for mesh

2016-03-28 Thread Bjorn Andersson
From: Jason Mobarak Patch "wcn36xx: Pad TIM PVM if needed" has caused a regression in mesh beaconing. The field tim_off is always 0 for mesh mode, and thus pvm_len (referring to the TIM length field) and pad are both incorrectly calculated. Thus, msg_body.beacon_length is incorrectly calculated