From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, sean.wang@mediatek.com
Subject: RE: [v2,1/3] Bluetooth: btusb: mediatek: use readx_poll_timeout instead of open coding
Date: Thu, 29 Sep 2022 21:01:30 -0700 (PDT) [thread overview]
Message-ID: <63366a1a.ca0a0220.2c6bb.0fbf@mx.google.com> (raw)
In-Reply-To: <ab8958da839ecadc0ebff9f0a221ef49a2e5a4cc.1664497281.git.objelf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 7144 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=682088
---Test result---
Test Summary:
CheckPatch PASS 4.64 seconds
GitLint FAIL 0.73 seconds
SubjectPrefix PASS 1.91 seconds
BuildKernel FAIL 34.02 seconds
BuildKernel32 FAIL 30.92 seconds
Incremental Build with patchesERROR 0.29 seconds
TestRunner: Setup PASS 514.02 seconds
TestRunner: l2cap-tester PASS 17.20 seconds
TestRunner: iso-tester PASS 16.20 seconds
TestRunner: bnep-tester PASS 6.49 seconds
TestRunner: mgmt-tester PASS 104.57 seconds
TestRunner: rfcomm-tester PASS 10.22 seconds
TestRunner: sco-tester PASS 9.74 seconds
TestRunner: ioctl-tester PASS 11.04 seconds
TestRunner: smp-tester PASS 9.73 seconds
TestRunner: userchan-tester PASS 6.80 seconds
Details
##############################
Test: GitLint - FAIL - 0.73 seconds
Run gitlint with rule in .gitlint
[v2,1/3] Bluetooth: btusb: mediatek: use readx_poll_timeout instead of open coding
1: T1 Title exceeds max length (82>80): "[v2,1/3] Bluetooth: btusb: mediatek: use readx_poll_timeout instead of open coding"
##############################
Test: BuildKernel - FAIL - 34.02 seconds
Build Kernel with minimal configuration supports Bluetooth
drivers/bluetooth/btmtk.c: In function ‘btmtk_coredump_notify’:
drivers/bluetooth/btmtk.c:111:7: error: ‘HCI_DEVCOREDUMP_ACTIVE’ undeclared (first use in this function); did you mean ‘BTMTK_COREDUMP_ACTIVE’?
111 | case HCI_DEVCOREDUMP_ACTIVE:
| ^~~~~~~~~~~~~~~~~~~~~~
| BTMTK_COREDUMP_ACTIVE
drivers/bluetooth/btmtk.c:111:7: note: each undeclared identifier is reported only once for each function it appears in
drivers/bluetooth/btmtk.c:114:7: error: ‘HCI_DEVCOREDUMP_TIMEOUT’ undeclared (first use in this function); did you mean ‘HCI_DISCONN_TIMEOUT’?
114 | case HCI_DEVCOREDUMP_TIMEOUT:
| ^~~~~~~~~~~~~~~~~~~~~~~
| HCI_DISCONN_TIMEOUT
drivers/bluetooth/btmtk.c:115:7: error: ‘HCI_DEVCOREDUMP_ABORT’ undeclared (first use in this function)
115 | case HCI_DEVCOREDUMP_ABORT:
| ^~~~~~~~~~~~~~~~~~~~~
drivers/bluetooth/btmtk.c:116:7: error: ‘HCI_DEVCOREDUMP_DONE’ undeclared (first use in this function)
116 | case HCI_DEVCOREDUMP_DONE:
| ^~~~~~~~~~~~~~~~~~~~
drivers/bluetooth/btmtk.c: In function ‘btmtk_register_coredump’:
drivers/bluetooth/btmtk.c:376:2: error: implicit declaration of function ‘hci_devcoredump_register’ [-Werror=implicit-function-declaration]
376 | hci_devcoredump_register(hdev, btmtk_coredump, btmtk_coredump_hdr,
| ^~~~~~~~~~~~~~~~~~~~~~~~
drivers/bluetooth/btmtk.c: In function ‘btmtk_process_coredump’:
drivers/bluetooth/btmtk.c:393:9: error: implicit declaration of function ‘hci_devcoredump_init’ [-Werror=implicit-function-declaration]
393 | err = hci_devcoredump_init(hdev, 1024000);
| ^~~~~~~~~~~~~~~~~~~~
drivers/bluetooth/btmtk.c:397:30: error: ‘struct hci_dev’ has no member named ‘dump’
397 | schedule_delayed_work(&hdev->dump.dump_timeout,
| ^~
drivers/bluetooth/btmtk.c:402:9: error: implicit declaration of function ‘hci_devcoredump_append’ [-Werror=implicit-function-declaration]
402 | err = hci_devcoredump_append(hdev, skb);
| ^~~~~~~~~~~~~~~~~~~~~~
drivers/bluetooth/btmtk.c:409:4: error: implicit declaration of function ‘hci_devcoredump_complete’ [-Werror=implicit-function-declaration]
409 | hci_devcoredump_complete(hdev);
| ^~~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:249: drivers/bluetooth/btmtk.o] Error 1
make[1]: *** [scripts/Makefile.build:465: drivers/bluetooth] Error 2
make: *** [Makefile:1855: drivers] Error 2
##############################
Test: BuildKernel32 - FAIL - 30.92 seconds
Build 32bit Kernel with minimal configuration supports Bluetooth
drivers/bluetooth/btmtk.c: In function ‘btmtk_coredump_notify’:
drivers/bluetooth/btmtk.c:111:7: error: ‘HCI_DEVCOREDUMP_ACTIVE’ undeclared (first use in this function); did you mean ‘BTMTK_COREDUMP_ACTIVE’?
111 | case HCI_DEVCOREDUMP_ACTIVE:
| ^~~~~~~~~~~~~~~~~~~~~~
| BTMTK_COREDUMP_ACTIVE
drivers/bluetooth/btmtk.c:111:7: note: each undeclared identifier is reported only once for each function it appears in
drivers/bluetooth/btmtk.c:114:7: error: ‘HCI_DEVCOREDUMP_TIMEOUT’ undeclared (first use in this function); did you mean ‘HCI_DISCONN_TIMEOUT’?
114 | case HCI_DEVCOREDUMP_TIMEOUT:
| ^~~~~~~~~~~~~~~~~~~~~~~
| HCI_DISCONN_TIMEOUT
drivers/bluetooth/btmtk.c:115:7: error: ‘HCI_DEVCOREDUMP_ABORT’ undeclared (first use in this function)
115 | case HCI_DEVCOREDUMP_ABORT:
| ^~~~~~~~~~~~~~~~~~~~~
drivers/bluetooth/btmtk.c:116:7: error: ‘HCI_DEVCOREDUMP_DONE’ undeclared (first use in this function)
116 | case HCI_DEVCOREDUMP_DONE:
| ^~~~~~~~~~~~~~~~~~~~
drivers/bluetooth/btmtk.c: In function ‘btmtk_register_coredump’:
drivers/bluetooth/btmtk.c:376:2: error: implicit declaration of function ‘hci_devcoredump_register’ [-Werror=implicit-function-declaration]
376 | hci_devcoredump_register(hdev, btmtk_coredump, btmtk_coredump_hdr,
| ^~~~~~~~~~~~~~~~~~~~~~~~
drivers/bluetooth/btmtk.c: In function ‘btmtk_process_coredump’:
drivers/bluetooth/btmtk.c:393:9: error: implicit declaration of function ‘hci_devcoredump_init’ [-Werror=implicit-function-declaration]
393 | err = hci_devcoredump_init(hdev, 1024000);
| ^~~~~~~~~~~~~~~~~~~~
drivers/bluetooth/btmtk.c:397:30: error: ‘struct hci_dev’ has no member named ‘dump’
397 | schedule_delayed_work(&hdev->dump.dump_timeout,
| ^~
drivers/bluetooth/btmtk.c:402:9: error: implicit declaration of function ‘hci_devcoredump_append’ [-Werror=implicit-function-declaration]
402 | err = hci_devcoredump_append(hdev, skb);
| ^~~~~~~~~~~~~~~~~~~~~~
drivers/bluetooth/btmtk.c:409:4: error: implicit declaration of function ‘hci_devcoredump_complete’ [-Werror=implicit-function-declaration]
409 | hci_devcoredump_complete(hdev);
| ^~~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:249: drivers/bluetooth/btmtk.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.29 seconds
Incremental build per patch in the series
buildkernel failed
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-09-30 4:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 0:23 [PATCH v2 1/3] Bluetooth: btusb: mediatek: use readx_poll_timeout instead of open coding sean.wang
2022-09-30 0:23 ` [PATCH v2 2/3] Bluetooth: btmtk: introduce btmtk reset work sean.wang
2022-09-30 0:23 ` [PATCH v2 3/3] Bluetooth: btusb: mediatek: add MediaTek devcoredump support sean.wang
2022-09-30 11:38 ` kernel test robot
2022-09-30 12:21 ` kernel test robot
2022-09-30 12:41 ` kernel test robot
2022-10-03 0:02 ` kernel test robot
2022-09-30 4:01 ` bluez.test.bot [this message]
2022-09-30 8:48 ` [PATCH v2 1/3] Bluetooth: btusb: mediatek: use readx_poll_timeout instead of open coding AngeloGioacchino Del Regno
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=63366a1a.ca0a0220.2c6bb.0fbf@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=sean.wang@mediatek.com \
/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).