From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, wse@tuxedocomputers.com
Subject: RE: Bluetooth: btintel: Add devices to HCI_QUIRK_BROKEN_LE_CODED
Date: Thu, 28 Mar 2024 06:56:20 -0700 (PDT) [thread overview]
Message-ID: <66057704.050a0220.52638.0edd@mx.google.com> (raw)
In-Reply-To: <20240328131800.63328-1-wse@tuxedocomputers.com>
[-- Attachment #1: Type: text/plain, Size: 3127 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=839335
---Test result---
Test Summary:
CheckPatch PASS 0.63 seconds
GitLint PASS 0.30 seconds
SubjectPrefix PASS 0.11 seconds
BuildKernel PASS 30.01 seconds
CheckAllWarning WARNING 33.22 seconds
CheckSparse WARNING 38.49 seconds
CheckSmatch FAIL 35.31 seconds
BuildKernel32 PASS 29.33 seconds
TestRunnerSetup PASS 523.44 seconds
TestRunner_l2cap-tester PASS 20.15 seconds
TestRunner_iso-tester PASS 37.19 seconds
TestRunner_bnep-tester PASS 6.26 seconds
TestRunner_mgmt-tester PASS 113.00 seconds
TestRunner_rfcomm-tester PASS 7.37 seconds
TestRunner_sco-tester PASS 14.87 seconds
TestRunner_ioctl-tester PASS 7.80 seconds
TestRunner_mesh-tester PASS 5.81 seconds
TestRunner_smp-tester PASS 6.85 seconds
TestRunner_userchan-tester PASS 4.96 seconds
IncrementalBuild PASS 32.67 seconds
Details
##############################
Test: CheckAllWarning - WARNING
Desc: Run linux kernel with all warning enabled
Output:
drivers/bluetooth/btintel.c: In function ‘btintel_setup_combined’:drivers/bluetooth/btintel.c:3034:3: warning: this statement may fall through [-Wimplicit-fallthrough=] 3034 | set_bit(HCI_QUIRK_BROKEN_LE_CODED, &hdev->quirks); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~drivers/bluetooth/btintel.c:3035:2: note: here 3035 | case 0x1b: | ^~~~
##############################
Test: CheckSparse - WARNING
Desc: Run sparse tool with linux kernel
Output:
drivers/bluetooth/btintel.c: In function ‘btintel_setup_combined’:drivers/bluetooth/btintel.c:3034:3: warning: this statement may fall through [-Wimplicit-fallthrough=]drivers/bluetooth/btintel.c:3035:2: note: here
##############################
Test: CheckSmatch - FAIL
Desc: Run smatch tool with source
Output:
Segmentation fault (core dumped)
make[4]: *** [scripts/Makefile.build:244: net/bluetooth/hci_core.o] Error 139
make[4]: *** Deleting file 'net/bluetooth/hci_core.o'
make[3]: *** [scripts/Makefile.build:485: net/bluetooth] Error 2
make[2]: *** [scripts/Makefile.build:485: net] Error 2
make[2]: *** Waiting for unfinished jobs....
Segmentation fault (core dumped)
make[4]: *** [scripts/Makefile.build:244: drivers/bluetooth/bcm203x.o] Error 139
make[4]: *** Deleting file 'drivers/bluetooth/bcm203x.o'
make[4]: *** Waiting for unfinished jobs....
make[3]: *** [scripts/Makefile.build:485: drivers/bluetooth] Error 2
make[2]: *** [scripts/Makefile.build:485: drivers] Error 2
make[1]: *** [/github/workspace/src/src/Makefile:1919: .] Error 2
make: *** [Makefile:240: __sub-make] Error 2
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2024-03-28 13:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 13:18 [PATCH] Bluetooth: btintel: Add devices to HCI_QUIRK_BROKEN_LE_CODED Werner Sembach
2024-03-28 13:23 ` Paul Menzel
2024-04-02 9:17 ` Christoffer Sandberg
2024-03-28 13:56 ` bluez.test.bot [this message]
2024-03-28 14:17 ` Luiz Augusto von Dentz
2024-03-28 23:20 ` Werner Sembach
2024-04-02 17:16 ` Pauli Virtanen
2024-04-03 17:32 ` Werner Sembach
2024-03-31 4:52 ` K, Kiran
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=66057704.050a0220.52638.0edd@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=wse@tuxedocomputers.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).