Hi,
On 02/25/2016 08:34 AM, Valo, Kalle wrote:
Peter Oh <poh@xxxxxxxxxxxxxxxx> writes:
Check and set Rx MAC timestamp when firmware indicates it.
Firmware adds it in Rx beacon frame only at this moment.
Driver and mac80211 may utilize it to detect such clockdrift
or beacon collision and use the result for beacon collision
avoidance.
Signed-off-by: Peter Oh <poh@xxxxxxxxxxxxxxxx>
---
v2:
- fix kbuild test robot warning, left shift count >= width of
type,
at __le32_to_cpu(arg.ext_info.rx_mac_timestamp_u32) << 32
v3:
- correct ext_info to start 4-byte aligned
- make struct wmi_mgmt_rx_ext_info 4-byte aligned to comply FW's
intention.
I see new warnings:
drivers/net/wireless/ath/ath10k/wmi.c:2199:16: warning: restricted __le32
degrades to integer
drivers/net/wireless/ath/ath10k/wmi.c:2201:41: warning: restricted __le32
degrades to integer
drivers/net/wireless/ath/ath10k/wmi.c:2201:41: warning: cast to restricted
__le32
drivers/net/wireless/ath/ath10k/wmi.c:2201:41: warning: restricted __le32
degrades to integer
Do I have a way to run this check before submitting a patch such as
checkpatch.pl?
Thanks,
Peter
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
