From: kbuild test robot <lkp@intel.com>
To: c_traja@qti.qualcomm.com
Cc: kbuild-all@01.org, ath10k@lists.infradead.org,
linux-wireless@vger.kernel.org, tamizhchelvam@codeaurora.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
robh@kernel.org, Tamizh chelvam <c_traja@qti.qualcomm.com>
Subject: Re: [PATCHv2 1/4] ath10k: Add support to enable or disable btcoex via nl80211
Date: Thu, 17 Nov 2016 21:51:35 +0800 [thread overview]
Message-ID: <201611172121.G6wtWwqI%fengguang.wu@intel.com> (raw)
In-Reply-To: <1479383064-25718-2-git-send-email-c_traja@qti.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 1967 bytes --]
Hi Tamizh,
[auto build test ERROR on ath6kl/ath-next]
[also build test ERROR on v4.9-rc5 next-20161117]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/c_traja-qti-qualcomm-com/ath10k-Add-support-for-BTCOEX-feature/20161117-200322
base: https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git ath-next
config: i386-allmodconfig (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
>> drivers/net/wireless/ath/ath10k/mac.c:7546:2: error: unknown field 'set_btcoex' specified in initializer
.set_btcoex = ath10k_mac_op_set_btcoex,
^
>> drivers/net/wireless/ath/ath10k/mac.c:7546:36: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
.set_btcoex = ath10k_mac_op_set_btcoex,
^~~~~~~~~~~~~~~~~~~~~~~~
drivers/net/wireless/ath/ath10k/mac.c:7546:36: note: (near initialization for 'ath10k_ops.reconfig_complete')
cc1: some warnings being treated as errors
vim +/set_btcoex +7546 drivers/net/wireless/ath/ath10k/mac.c
7540 .add_chanctx = ath10k_mac_op_add_chanctx,
7541 .remove_chanctx = ath10k_mac_op_remove_chanctx,
7542 .change_chanctx = ath10k_mac_op_change_chanctx,
7543 .assign_vif_chanctx = ath10k_mac_op_assign_vif_chanctx,
7544 .unassign_vif_chanctx = ath10k_mac_op_unassign_vif_chanctx,
7545 .switch_vif_chanctx = ath10k_mac_op_switch_vif_chanctx,
> 7546 .set_btcoex = ath10k_mac_op_set_btcoex,
7547
7548 CFG80211_TESTMODE_CMD(ath10k_tm_cmd)
7549
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 56822 bytes --]
next prev parent reply other threads:[~2016-11-17 17:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 11:44 [PATCHv2 0/4] ath10k: Add support for BTCOEX feature c_traja
2016-11-17 11:44 ` [PATCHv2 1/4] ath10k: Add support to enable or disable btcoex via nl80211 c_traja
2016-11-17 13:51 ` kbuild test robot [this message]
2016-11-17 11:44 ` [PATCHv2 2/4] ath10k: Add support to update btcoex priority value " c_traja
2016-11-17 14:36 ` kbuild test robot
2016-11-17 11:44 ` [PATCHv2 3/4] dt: bindings: add new dt entry for BTCOEX feature in qcom,ath10k.txt c_traja
2016-11-18 14:44 ` Rob Herring
2016-11-23 10:20 ` Tamizh chelvam
2016-11-17 11:44 ` [PATCHv2 4/4] ath10k: Add support to read btcoex related data from DT c_traja
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201611172121.G6wtWwqI%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=ath10k@lists.infradead.org \
--cc=c_traja@qti.qualcomm.com \
--cc=devicetree@vger.kernel.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tamizhchelvam@codeaurora.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).