From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, 15013537245@163.com
Subject: RE: Bluetooth: hci_sync: fix BR/EDR wakeup bug
Date: Thu, 14 Dec 2023 01:56:58 -0800 (PST) [thread overview]
Message-ID: <657ad16a.c80a0220.e4657.e618@mx.google.com> (raw)
In-Reply-To: <20231214092255.1018859-1-15013537245@163.com>
[-- Attachment #1: Type: text/plain, Size: 2185 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=809975
---Test result---
Test Summary:
CheckPatch FAIL 0.96 seconds
GitLint PASS 0.33 seconds
SubjectPrefix PASS 0.13 seconds
BuildKernel PASS 28.56 seconds
CheckAllWarning PASS 29.75 seconds
CheckSparse PASS 34.91 seconds
CheckSmatch PASS 98.52 seconds
BuildKernel32 PASS 26.37 seconds
TestRunnerSetup PASS 413.84 seconds
TestRunner_l2cap-tester PASS 22.71 seconds
TestRunner_iso-tester PASS 48.05 seconds
TestRunner_bnep-tester PASS 6.95 seconds
TestRunner_mgmt-tester PASS 160.64 seconds
TestRunner_rfcomm-tester PASS 10.93 seconds
TestRunner_sco-tester PASS 14.39 seconds
TestRunner_ioctl-tester PASS 11.79 seconds
TestRunner_mesh-tester PASS 9.62 seconds
TestRunner_smp-tester PASS 9.78 seconds
TestRunner_userchan-tester PASS 7.24 seconds
IncrementalBuild PASS 25.36 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
Bluetooth: hci_sync: fix BR/EDR wakeup bug
WARNING: 'comming' may be misspelled - perhaps 'coming'?
#51:
has hci mode change event comming,it cause controller can not enter
^^^^^^^
total: 0 errors, 1 warnings, 0 checks, 18 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/13492648.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-12-14 9:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 9:22 [PATCH] Bluetooth: hci_sync: fix BR/EDR wakeup bug 15013537245
2023-12-14 9:56 ` bluez.test.bot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-18 10:24 15013537245
2023-12-18 11:00 ` bluez.test.bot
2023-12-05 2:41 [PATCH] " 15013537245
2023-12-05 3:33 ` bluez.test.bot
2023-11-27 9:05 [PATCH] " 15013537245
2023-11-27 9:33 ` 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=657ad16a.c80a0220.e4657.e618@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=15013537245@163.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).