From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, johan+linaro@kernel.org
Subject: RE: Bluetooth: qca: fix invalid device address check
Date: Tue, 16 Apr 2024 02:56:52 -0700 (PDT) [thread overview]
Message-ID: <661e4b64.050a0220.a88ce.9d1a@mx.google.com> (raw)
In-Reply-To: <20240416091509.19995-1-johan+linaro@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 3831 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=844980
---Test result---
Test Summary:
CheckPatch FAIL 1.22 seconds
GitLint FAIL 0.50 seconds
SubjectPrefix PASS 0.10 seconds
BuildKernel PASS 30.99 seconds
CheckAllWarning PASS 33.15 seconds
CheckSparse PASS 39.27 seconds
CheckSmatch FAIL 35.66 seconds
BuildKernel32 PASS 29.47 seconds
TestRunnerSetup PASS 531.53 seconds
TestRunner_l2cap-tester PASS 20.80 seconds
TestRunner_iso-tester PASS 31.43 seconds
TestRunner_bnep-tester PASS 4.94 seconds
TestRunner_mgmt-tester PASS 112.59 seconds
TestRunner_rfcomm-tester PASS 7.62 seconds
TestRunner_sco-tester PASS 15.30 seconds
TestRunner_ioctl-tester PASS 7.89 seconds
TestRunner_mesh-tester PASS 6.04 seconds
TestRunner_smp-tester PASS 7.04 seconds
TestRunner_userchan-tester PASS 5.12 seconds
IncrementalBuild PASS 28.25 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
Bluetooth: qca: fix invalid device address check
WARNING: Reported-by: should be immediately followed by Closes: with a URL to the report
#85:
Reported-by: Janaki Ramaiah Thota <quic_janathot@quicinc.com>
Link: https://lore.kernel.org/r/124a7d54-5a18-4be7-9a76-a12017f6cce5@quicinc.com/
total: 0 errors, 1 warnings, 64 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.
/github/workspace/src/src/13631544.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:
Bluetooth: qca: fix invalid device address check
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
23: B1 Line exceeds max length (81>80): "Link: https://lore.kernel.org/r/124a7d54-5a18-4be7-9a76-a12017f6cce5@quicinc.com/"
24: B3 Line contains hard tab characters (\t): "Cc: stable@vger.kernel.org # 6.5"
##############################
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-04-16 9:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 9:15 [PATCH] Bluetooth: qca: fix invalid device address check Johan Hovold
2024-04-16 9:56 ` bluez.test.bot [this message]
2024-04-16 15:10 ` patchwork-bot+bluetooth
2024-04-22 17:50 ` Doug Anderson
2024-04-23 9:08 ` Johan Hovold
2024-04-23 15:09 ` Doug Anderson
2024-04-25 8:40 ` Johan Hovold
2024-04-25 15:01 ` Janaki Ramaiah Thota
2024-04-25 15:58 ` Johan Hovold
2024-04-26 6:23 ` Janaki Ramaiah Thota
2024-04-26 10:42 ` Janaki Ramaiah Thota
2024-04-26 12:45 ` Johan Hovold
2024-04-26 14:15 ` Johan Hovold
2024-04-25 15:22 ` Doug Anderson
2024-04-25 16:13 ` Johan Hovold
2024-04-25 16:19 ` Doug Anderson
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=661e4b64.050a0220.a88ce.9d1a@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=johan+linaro@kernel.org \
--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