From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, kiran.k@intel.com
Subject: RE: [v1,1/3] Bluetooth: btintel: Export few static functions
Date: Thu, 28 Mar 2024 04:31:06 -0700 (PDT) [thread overview]
Message-ID: <660554fa.650a0220.9f132.1fa6@mx.google.com> (raw)
In-Reply-To: <20240328111904.992068-1-kiran.k@intel.com>
[-- Attachment #1: Type: text/plain, Size: 3018 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=839288
---Test result---
Test Summary:
CheckPatch FAIL 4.21 seconds
GitLint PASS 0.68 seconds
SubjectPrefix PASS 0.24 seconds
BuildKernel PASS 29.53 seconds
CheckAllWarning PASS 32.04 seconds
CheckSparse PASS 41.07 seconds
CheckSmatch FAIL 34.86 seconds
BuildKernel32 PASS 28.59 seconds
TestRunnerSetup PASS 519.70 seconds
TestRunner_l2cap-tester PASS 18.11 seconds
TestRunner_iso-tester PASS 29.94 seconds
TestRunner_bnep-tester PASS 4.70 seconds
TestRunner_mgmt-tester PASS 112.06 seconds
TestRunner_rfcomm-tester PASS 7.26 seconds
TestRunner_sco-tester PASS 14.88 seconds
TestRunner_ioctl-tester PASS 7.68 seconds
TestRunner_mesh-tester PASS 5.74 seconds
TestRunner_smp-tester PASS 6.78 seconds
TestRunner_userchan-tester PASS 4.90 seconds
IncrementalBuild PASS 38.98 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[v1,2/3] Bluetooth: btintel_pcie: Add support for PCIE transport
WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
#152:
new file mode 100644
total: 0 errors, 1 warnings, 1801 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/13608400.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: 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
prev parent reply other threads:[~2024-03-28 11:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 11:19 [PATCH v1 1/3] Bluetooth: btintel: Export few static functions Kiran K
2024-03-28 11:19 ` [PATCH v1 2/3] Bluetooth: btintel_pcie: Add support for PCIE transport Kiran K
2024-03-28 12:24 ` Paul Menzel
2024-05-07 13:34 ` K, Kiran
2024-05-07 20:28 ` Luiz Augusto von Dentz
2024-03-28 14:09 ` Luiz Augusto von Dentz
2024-03-28 14:13 ` Luiz Augusto von Dentz
2024-05-07 14:39 ` K, Kiran
2024-03-28 17:08 ` Bjorn Helgaas
2024-05-07 13:47 ` K, Kiran
2024-03-28 11:19 ` [PATCH v1 3/3] Bluetooth: btintel_pcie: Add *setup* function to download firmware Kiran K
2024-03-28 17:08 ` Bjorn Helgaas
2024-05-07 13:59 ` K, Kiran
2024-05-08 2:03 ` Bjorn Helgaas
2024-05-08 2:04 ` Bjorn Helgaas
2024-03-28 11:31 ` bluez.test.bot [this message]
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=660554fa.650a0220.9f132.1fa6@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=kiran.k@intel.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;
as well as URLs for NNTP newsgroup(s).