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: [PATCH] Bluetooth: bpa10x: Use h4_recv_buf helper for frame reassembly
Date: Thu, 8 Oct 2015 09:24:01 +0800 [thread overview]
Message-ID: <201510080913.3hUhkhTC%fengguang.wu@intel.com> (raw)
In-Reply-To: <1444266413-77165-1-git-send-email-marcel@holtmann.org>
[-- Attachment #1: Type: text/plain, Size: 1059 bytes --]
Hi Marcel,
[auto build test ERROR on v4.3-rc4 -- if it's inappropriate base, please ignore]
config: i386-allmodconfig (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
>> drivers/bluetooth/bpa10x.c:96:29: error: 'hci_recv_diag' undeclared here (not in a function)
{ HCI_RECV_VENDOR, .recv = hci_recv_diag },
^
vim +/hci_recv_diag +96 drivers/bluetooth/bpa10x.c
90 .maxlen = HCI_MAX_FRAME_SIZE
91
92 static const struct h4_recv_pkt bpa10x_recv_pkts[] = {
93 { H4_RECV_ACL, .recv = hci_recv_frame },
94 { H4_RECV_SCO, .recv = hci_recv_frame },
95 { H4_RECV_EVENT, .recv = hci_recv_frame },
> 96 { HCI_RECV_VENDOR, .recv = hci_recv_diag },
97 };
98
99 static void bpa10x_rx_complete(struct urb *urb)
---
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: 51590 bytes --]
next prev parent reply other threads:[~2015-10-08 1:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 1:06 [PATCH] Bluetooth: bpa10x: Use h4_recv_buf helper for frame reassembly Marcel Holtmann
2015-10-08 1:24 ` kbuild test robot [this message]
2015-10-08 1:27 ` kbuild test robot
2015-10-08 7:05 ` 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=201510080913.3hUhkhTC%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