From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, hildawu@realtek.com
Subject: RE: Bluetooth: btusb: Add Realtek devcoredump support
Date: Thu, 22 Sep 2022 04:10:50 -0700 (PDT) [thread overview]
Message-ID: <632c42ba.920a0220.ac36c.2705@mx.google.com> (raw)
In-Reply-To: <20220922103337.26167-1-hildawu@realtek.com>
[-- Attachment #1: Type: text/plain, Size: 3618 bytes --]
This is automated email and please do not reply to this email!
Dear submitter,
Thank you for submitting the patches to the linux bluetooth mailing list.
This is a CI test results with your patch series:
PW Link:https://patchwork.kernel.org/project/bluetooth/list/?series=679375
---Test result---
Test Summary:
CheckPatch PASS 2.02 seconds
GitLint PASS 0.82 seconds
SubjectPrefix PASS 0.76 seconds
BuildKernel FAIL 31.01 seconds
BuildKernel32 FAIL 27.10 seconds
Incremental Build with patchesERROR 0.32 seconds
TestRunner: Setup PASS 513.22 seconds
TestRunner: l2cap-tester PASS 17.21 seconds
TestRunner: iso-tester PASS 16.16 seconds
TestRunner: bnep-tester PASS 6.50 seconds
TestRunner: mgmt-tester PASS 105.37 seconds
TestRunner: rfcomm-tester PASS 10.33 seconds
TestRunner: sco-tester PASS 9.77 seconds
TestRunner: smp-tester PASS 9.70 seconds
TestRunner: userchan-tester PASS 6.78 seconds
Details
##############################
Test: BuildKernel - FAIL - 31.01 seconds
Build Kernel with minimal configuration supports Bluetooth
drivers/bluetooth/btusb.c: In function ‘btusb_rtl_cmd_timeout’:
drivers/bluetooth/btusb.c:745:7: error: implicit declaration of function ‘hci_devcoredump_init’ [-Werror=implicit-function-declaration]
745 | if (!hci_devcoredump_init(hdev, skb->len)) {
| ^~~~~~~~~~~~~~~~~~~~
drivers/bluetooth/btusb.c:746:3: error: implicit declaration of function ‘hci_devcoredump_append’ [-Werror=implicit-function-declaration]
746 | hci_devcoredump_append(hdev, skb);
| ^~~~~~~~~~~~~~~~~~~~~~
drivers/bluetooth/btusb.c:747:3: error: implicit declaration of function ‘hci_devcoredump_complete’ [-Werror=implicit-function-declaration]
747 | hci_devcoredump_complete(hdev);
| ^~~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:249: drivers/bluetooth/btusb.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [scripts/Makefile.build:465: drivers/bluetooth] Error 2
make: *** [Makefile:1855: drivers] Error 2
##############################
Test: BuildKernel32 - FAIL - 27.10 seconds
Build 32bit Kernel with minimal configuration supports Bluetooth
drivers/bluetooth/btusb.c: In function ‘btusb_rtl_cmd_timeout’:
drivers/bluetooth/btusb.c:745:7: error: implicit declaration of function ‘hci_devcoredump_init’ [-Werror=implicit-function-declaration]
745 | if (!hci_devcoredump_init(hdev, skb->len)) {
| ^~~~~~~~~~~~~~~~~~~~
drivers/bluetooth/btusb.c:746:3: error: implicit declaration of function ‘hci_devcoredump_append’ [-Werror=implicit-function-declaration]
746 | hci_devcoredump_append(hdev, skb);
| ^~~~~~~~~~~~~~~~~~~~~~
drivers/bluetooth/btusb.c:747:3: error: implicit declaration of function ‘hci_devcoredump_complete’ [-Werror=implicit-function-declaration]
747 | hci_devcoredump_complete(hdev);
| ^~~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:249: drivers/bluetooth/btusb.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [scripts/Makefile.build:465: drivers/bluetooth] Error 2
make: *** [Makefile:1855: drivers] Error 2
##############################
Test: Incremental Build with patches - SKIPPED - 0.32 seconds
Incremental build per patch in the series
buildkernel failed
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-09-22 11:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 10:33 [PATCH] Bluetooth: btusb: Add Realtek devcoredump support hildawu
2022-09-22 11:10 ` bluez.test.bot [this message]
2022-09-22 23:54 ` kernel test robot
2022-09-23 2:48 ` kernel test robot
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=632c42ba.920a0220.ac36c.2705@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=hildawu@realtek.com \
--cc=linux-bluetooth@vger.kernel.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