From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, iulia.tanasescu@nxp.com
Subject: RE: Add support for handling encrypted BIGs based on BIGInfo reports
Date: Mon, 21 Aug 2023 05:49:06 -0700 (PDT) [thread overview]
Message-ID: <64e35d42.050a0220.f83fe.81c2@mx.google.com> (raw)
In-Reply-To: <20230821120014.28654-2-iulia.tanasescu@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 2668 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=777862
---Test result---
Test Summary:
CheckPatch FAIL 7.08 seconds
GitLint PASS 0.76 seconds
SubjectPrefix PASS 0.26 seconds
BuildKernel PASS 40.50 seconds
CheckAllWarning PASS 44.08 seconds
CheckSparse WARNING 50.02 seconds
CheckSmatch WARNING 135.66 seconds
BuildKernel32 PASS 38.60 seconds
TestRunnerSetup PASS 586.89 seconds
TestRunner_l2cap-tester PASS 33.68 seconds
TestRunner_iso-tester PASS 69.55 seconds
TestRunner_bnep-tester PASS 13.64 seconds
TestRunner_mgmt-tester PASS 257.14 seconds
TestRunner_rfcomm-tester PASS 20.40 seconds
TestRunner_sco-tester PASS 24.45 seconds
TestRunner_ioctl-tester PASS 23.13 seconds
TestRunner_mesh-tester PASS 17.27 seconds
TestRunner_smp-tester PASS 18.23 seconds
TestRunner_userchan-tester PASS 14.51 seconds
IncrementalBuild PASS 71.39 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[1/2] Bluetooth: ISO: Add MGMT event for BIGInfo adv report
WARNING: please, no spaces at the start of a line
#130: FILE: include/net/bluetooth/mgmt.h:6:
+ Copyright 2023 NXP$
WARNING: please, no spaces at the start of a line
#183: FILE: net/bluetooth/mgmt.c:6:
+ Copyright 2023 NXP$
total: 0 errors, 2 warnings, 0 checks, 70 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/13359355.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):
##############################
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-08-21 12:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 12:00 [PATCH 0/2] Add support for handling encrypted BIGs based on BIGInfo reports Iulia Tanasescu
2023-08-21 12:00 ` [PATCH 1/2] Bluetooth: ISO: Add MGMT event for BIGInfo adv report Iulia Tanasescu
2023-08-21 12:49 ` bluez.test.bot [this message]
2023-08-21 12:00 ` [PATCH 2/2] Bluetooth: ISO: Pass sync_handle through iso qos Iulia Tanasescu
-- strict thread matches above, loose matches on Subject: below --
2023-08-24 10:16 [PATCH 1/2] Bluetooth: ISO: Add MGMT event for BIGInfo adv report Iulia Tanasescu
2023-08-24 11:02 ` Add support for handling encrypted BIGs based on BIGInfo reports bluez.test.bot
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=64e35d42.050a0220.f83fe.81c2@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.