From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, iulia.tanasescu@nxp.com
Subject: RE: Bluetooth: Add support for creating multiple BISes
Date: Wed, 17 May 2023 00:57:10 -0700 (PDT) [thread overview]
Message-ID: <646488d6.050a0220.34caf.6ea3@mx.google.com> (raw)
In-Reply-To: <20230517072706.5988-2-iulia.tanasescu@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 2712 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=748305
---Test result---
Test Summary:
CheckPatch FAIL 5.46 seconds
GitLint PASS 0.30 seconds
SubjectPrefix PASS 0.11 seconds
BuildKernel PASS 32.19 seconds
CheckAllWarning PASS 35.31 seconds
CheckSparse WARNING 40.44 seconds
CheckSmatch WARNING 109.45 seconds
BuildKernel32 PASS 31.65 seconds
TestRunnerSetup PASS 453.92 seconds
TestRunner_l2cap-tester PASS 17.19 seconds
TestRunner_iso-tester PASS 21.60 seconds
TestRunner_bnep-tester PASS 5.70 seconds
TestRunner_mgmt-tester PASS 115.16 seconds
TestRunner_rfcomm-tester PASS 9.01 seconds
TestRunner_sco-tester PASS 8.41 seconds
TestRunner_ioctl-tester PASS 9.73 seconds
TestRunner_mesh-tester PASS 7.14 seconds
TestRunner_smp-tester PASS 8.22 seconds
TestRunner_userchan-tester PASS 5.94 seconds
IncrementalBuild PASS 29.80 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[1/1] Bluetooth: Add support for creating multiple BISes
WARNING: please, no spaces at the start of a line
#505: FILE: net/bluetooth/hci_core.c:5:
+ Copyright 2023 NXP$
CHECK: Avoid CamelCase: <Copyright>
#505: FILE: net/bluetooth/hci_core.c:5:
+ Copyright 2023 NXP
total: 0 errors, 1 warnings, 1 checks, 542 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/13244298.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: CheckSparse - WARNING
Desc: Run sparse tool with linux kernel
Output:
net/bluetooth/hci_event.c: note: in included file (through include/net/bluetooth/hci_core.h):net/bluetooth/hci_event.c:6964:40: warning: cast to restricted __le16
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
net/bluetooth/hci_event.c: note: in included file (through include/net/bluetooth/hci_core.h):
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-05-17 7:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 7:27 [PATCH 0/1] Bluetooth: Add support for creating multiple BISes Iulia Tanasescu
2023-05-17 7:27 ` [PATCH 1/1] " Iulia Tanasescu
2023-05-17 7:33 ` Paul Menzel
2023-05-18 7:19 ` Iulia Tanasescu
2023-05-17 7:57 ` bluez.test.bot [this message]
2023-05-17 17:55 ` Luiz Augusto von Dentz
2023-05-18 7:15 ` Iulia Tanasescu
2023-05-18 17:13 ` Luiz Augusto von Dentz
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=646488d6.050a0220.34caf.6ea3@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=iulia.tanasescu@nxp.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).