From: kbuild test robot <lkp@intel.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: kbuild-all@01.org, linux-bluetooth@vger.kernel.org
Subject: Re: [RFC] Bluetooth: btusb: Add support for Broadcom LM_DIAG interface
Date: Fri, 9 Oct 2015 02:39:26 +0800 [thread overview]
Message-ID: <201510090259.MXd0LzVd%fengguang.wu@intel.com> (raw)
In-Reply-To: <1444328588-122301-1-git-send-email-marcel@holtmann.org>
[-- Attachment #1: Type: text/plain, Size: 1667 bytes --]
Hi Marcel,
[auto build test ERROR on v4.3-rc4 -- if it's inappropriate base, please ignore]
config: xtensa-allyesconfig (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=xtensa
All errors (new ones prefixed by >>):
drivers/bluetooth/btusb.c: In function 'btusb_diag_complete':
drivers/bluetooth/btusb.c:893:4: error: implicit declaration of function 'hci_recv_diag' [-Werror=implicit-function-declaration]
hci_recv_diag(hdev, skb);
^
drivers/bluetooth/btusb.c: In function 'btusb_probe':
>> drivers/bluetooth/btusb.c:2883:7: error: 'struct hci_dev' has no member named 'set_diag'
hdev->set_diag = btusb_bcm_set_diag;
^
drivers/bluetooth/btusb.c:2892:7: error: 'struct hci_dev' has no member named 'set_diag'
hdev->set_diag = btusb_bcm_set_diag;
^
cc1: some warnings being treated as errors
vim +2883 drivers/bluetooth/btusb.c
2877 if (id->driver_info & BTUSB_BCM92035)
2878 hdev->setup = btusb_setup_bcm92035;
2879
2880 #ifdef CONFIG_BT_HCIBTUSB_BCM
2881 if (id->driver_info & BTUSB_BCM_PATCHRAM) {
2882 hdev->setup = btbcm_setup_patchram;
> 2883 hdev->set_diag = btusb_bcm_set_diag;
2884 hdev->set_bdaddr = btbcm_set_bdaddr;
2885
2886 /* Broadcom LM_DIAG Interface numbers are hardcoded */
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 42410 bytes --]
next prev parent reply other threads:[~2015-10-08 18:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 18:23 [RFC] Bluetooth: btusb: Add support for Broadcom LM_DIAG interface Marcel Holtmann
2015-10-08 18:38 ` kbuild test robot
2015-10-08 18:39 ` kbuild test robot [this message]
2015-10-09 11:31 ` Johan Hedberg
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=201510090259.MXd0LzVd%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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).