From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, Nobuaki.Tsunashima@infineon.com
Subject: RE: [v2] Patch for CYW4373 hci up fail issue
Date: Mon, 20 May 2024 01:58:09 -0700 (PDT) [thread overview]
Message-ID: <664b10a1.0c0a0220.f0d0c.3e80@mx.google.com> (raw)
In-Reply-To: <016dd2b28cd5435ba6f13b01d4da0d44@infineon.com>
[-- Attachment #1: Type: text/plain, Size: 5691 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=854351
---Test result---
Test Summary:
CheckPatch FAIL 1.29 seconds
GitLint FAIL 0.54 seconds
SubjectPrefix FAIL 0.35 seconds
BuildKernel PASS 31.19 seconds
CheckAllWarning PASS 34.29 seconds
CheckSparse PASS 39.28 seconds
CheckSmatch FAIL 36.39 seconds
BuildKernel32 PASS 29.13 seconds
TestRunnerSetup PASS 534.76 seconds
TestRunner_l2cap-tester PASS 18.82 seconds
TestRunner_iso-tester FAIL 33.51 seconds
TestRunner_bnep-tester PASS 4.84 seconds
TestRunner_mgmt-tester FAIL 110.56 seconds
TestRunner_rfcomm-tester PASS 7.54 seconds
TestRunner_sco-tester PASS 15.07 seconds
TestRunner_ioctl-tester PASS 8.13 seconds
TestRunner_mesh-tester PASS 6.02 seconds
TestRunner_smp-tester PASS 7.20 seconds
TestRunner_userchan-tester PASS 4.96 seconds
IncrementalBuild PASS 28.38 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[v2] Patch for CYW4373 hci up fail issue
WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#80:
CYW4373 ROM FW has an issue that it claims LE_Read_Transmit_Power command as supported in a response
ERROR: trailing whitespace
#116: FILE: drivers/bluetooth/btbcm.c:452:
+^Iconst struct bcm_chip_version_table *entry = $
WARNING: line length of 107 exceeds 100 columns
#117: FILE: drivers/bluetooth/btbcm.c:453:
+ &disable_broken_read_transmit_power_by_chip_ver[0];
ERROR: that open brace { should be on the previous line
#119: FILE: drivers/bluetooth/btbcm.c:455:
+ for (i = 0 ; i < table_size ; i++, entry++)
+ {
WARNING: From:/Signed-off-by: email name mismatch: 'From: Nobuaki.Tsunashima@infineon.com' != 'Signed-off-by: Nobuaki Tsunashima <nobuaki.tsunashima@infineon.com>'
total: 2 errors, 3 warnings, 60 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
NOTE: Whitespace errors detected.
You may wish to use scripts/cleanpatch or scripts/cleanfile
/github/workspace/src/src/13668129.patch has style problems, please review.
NOTE: Ignored message types: UNKNOWN_COMMIT_ID
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[v2] Patch for CYW4373 hci up fail issue
WARNING: I3 - ignore-body-lines: gitlint will be switching from using Python regex 'match' (match beginning) to 'search' (match anywhere) semantics. Please review your ignore-body-lines.regex option accordingly. To remove this warning, set general.regex-style-search=True. More details: https://jorisroovers.github.io/gitlint/configuration/#regex-style-search
3: B1 Line exceeds max length (100>80): "CYW4373 ROM FW has an issue that it claims LE_Read_Transmit_Power command as supported in a response"
4: B1 Line exceeds max length (91>80): "of Read_Local_Supported_Command command but rejects the LE_Read_Transmit_Power command with"
7: B1 Line exceeds max length (110>80): "Especially in USB i/f case, it would be difficult to download patch FW that includes Its fix unless hci is up."
8: B1 Line exceeds max length (99>80): "The patch forces the driver to skip LE_Read_Transmit_Power Command when it detects CYW4373 with ROM"
##############################
Test: SubjectPrefix - FAIL
Desc: Check subject contains "Bluetooth" prefix
Output:
"Bluetooth: " prefix is not specified in the subject
##############################
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....
Segmentation fault (core dumped)
make[4]: *** [scripts/Makefile.build:244: drivers/bluetooth/bpa10x.o] Error 139
make[4]: *** Deleting file 'drivers/bluetooth/bpa10x.o'
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
##############################
Test: TestRunner_iso-tester - FAIL
Desc: Run iso-tester with test-runner
Output:
Total: 122, Passed: 117 (95.9%), Failed: 1, Not Run: 4
Failed Test Cases
ISO Connect2 Suspend - Success Failed 4.239 seconds
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 492, Passed: 489 (99.4%), Failed: 1, Not Run: 2
Failed Test Cases
LL Privacy - Remove Device 4 (Disable Adv) Timed out 2.734 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2024-05-20 8:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-20 8:22 [PATCH v2] Patch for CYW4373 hci up fail issue Nobuaki.Tsunashima
2024-05-20 8:58 ` bluez.test.bot [this message]
2024-05-20 16:52 ` Paul Menzel
2024-05-21 1:43 ` Nobuaki.Tsunashima
2024-05-22 4:19 ` Paul Menzel
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=664b10a1.0c0a0220.f0d0c.3e80@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=Nobuaki.Tsunashima@infineon.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