From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, claudia.rosu@nxp.com
Subject: RE: Bluetooth: hci_sync: Enable events for BIS capable device
Date: Thu, 29 Jun 2023 03:35:01 -0700 (PDT) [thread overview]
Message-ID: <649d5e55.9d0a0220.90ea7.b4ff@mx.google.com> (raw)
In-Reply-To: <20230629094120.5463-2-claudia.rosu@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 2104 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=761184
---Test result---
Test Summary:
CheckPatch FAIL 0.86 seconds
GitLint PASS 0.29 seconds
SubjectPrefix PASS 0.11 seconds
BuildKernel PASS 32.47 seconds
CheckAllWarning PASS 35.28 seconds
CheckSparse PASS 39.76 seconds
CheckSmatch PASS 112.05 seconds
BuildKernel32 PASS 31.27 seconds
TestRunnerSetup PASS 448.16 seconds
TestRunner_l2cap-tester PASS 17.05 seconds
TestRunner_iso-tester PASS 22.63 seconds
TestRunner_bnep-tester PASS 5.48 seconds
TestRunner_mgmt-tester PASS 128.48 seconds
TestRunner_rfcomm-tester PASS 8.72 seconds
TestRunner_sco-tester PASS 8.02 seconds
TestRunner_ioctl-tester PASS 9.23 seconds
TestRunner_mesh-tester PASS 6.89 seconds
TestRunner_smp-tester PASS 8.01 seconds
TestRunner_userchan-tester PASS 5.75 seconds
IncrementalBuild PASS 29.93 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[v2,1/1] Bluetooth: hci_sync: Enable events for BIS capable devices
WARNING: Missing commit description - Add an appropriate one
total: 0 errors, 1 warnings, 0 checks, 13 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/13296835.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.
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-06-29 10:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 9:41 [PATCH v2 0/1] Bluetooth: hci_sync: Enable events for BIS capable device Claudia Draghicescu
2023-06-29 9:41 ` [PATCH v2 1/1] Bluetooth: hci_sync: Enable events for BIS capable devices Claudia Draghicescu
2023-06-29 10:35 ` bluez.test.bot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-29 13:45 [PATCH v3 " Claudia Draghicescu
2023-06-29 14:36 ` Bluetooth: hci_sync: Enable events for BIS capable device bluez.test.bot
2023-06-29 8:37 [PATCH 1/1] Bluetooth: hci_sync: Enable events for BIS capable devices Claudia Draghicescu
2023-06-29 9:40 ` Bluetooth: hci_sync: Enable events for BIS capable device 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=649d5e55.9d0a0220.90ea7.b4ff@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=claudia.rosu@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.