kbuild test robot <[email protected]> writes:

> Hi Mohammed,
>
> [auto build test ERROR on wireless-drivers-next/master]
> [also build test ERROR on next-20160309]
> [cannot apply to v4.5-rc7]
> [if your patch is applied to the wrong git tree, please drop us a note to 
> help improving the system]
>
> url:    
> https://github.com/0day-ci/linux/commits/Mohammed-Shafi-Shajakhan/ath10k-Add-support-for-ath10k_sta_statistics-support/20160309-153522
> base:   
> https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next.git
>  master
> config: sparc64-allmodconfig (attached as .config)
> reproduce:
>         wget 
> https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross
>  -O ~/bin/make.cross
>         chmod +x ~/bin/make.cross
>         # save the attached .config to linux build tree
>         make.cross ARCH=sparc64 
>
> All errors (new ones prefixed by >>):
>
>    drivers/net/wireless/ath/ath10k/debugfs_sta.c: In function 
> 'ath10k_sta_statistics':
>>> drivers/net/wireless/ath/ath10k/debugfs_sta.c:51:2: error: implicit 
>>> declaration of function 'ath10k_peer_stats_enabled' 
>>> [-Werror=implicit-function-declaration]
>      if (!ath10k_peer_stats_enabled(ar))
>      ^
>>> drivers/net/wireless/ath/ath10k/debugfs_sta.c:54:7: error: 'struct 
>>> station_info' has no member named 'rx_duration'
>      sinfo->rx_duration = arsta->rx_duration;
>           ^
>>> drivers/net/wireless/ath/ath10k/debugfs_sta.c:55:27: error: 
>>> 'NL80211_STA_INFO_RX_DURATION' undeclared (first use in this function)
>      sinfo->filled |= 1ULL << NL80211_STA_INFO_RX_DURATION;
>                               ^
>    drivers/net/wireless/ath/ath10k/debugfs_sta.c:55:27: note: each undeclared 
> identifier is reported only once for each function it appears in
>    cc1: some warnings being treated as errors

This is expected as the patches depend on mac80211 patches.

-- 
Kalle Valo--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to