From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, yinghsu@chromium.org
Subject: RE: Bluetooth: Add default wakeup callback for HCI UART driver
Date: Mon, 04 Jul 2022 04:07:02 -0700 (PDT) [thread overview]
Message-ID: <62c2c9d6.1c69fb81.9177.d9be@mx.google.com> (raw)
In-Reply-To: <20220704183320.1.Ib7423c21f71003643a5bbe954ed0538ee532b29c@changeid>
[-- Attachment #1: Type: text/plain, Size: 2041 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=656284
---Test result---
Test Summary:
CheckPatch FAIL 1.75 seconds
GitLint PASS 0.96 seconds
SubjectPrefix PASS 0.80 seconds
BuildKernel PASS 31.48 seconds
BuildKernel32 PASS 26.88 seconds
Incremental Build with patchesPASS 37.68 seconds
TestRunner: Setup PASS 463.74 seconds
TestRunner: l2cap-tester PASS 16.58 seconds
TestRunner: bnep-tester PASS 5.69 seconds
TestRunner: mgmt-tester PASS 94.94 seconds
TestRunner: rfcomm-tester PASS 9.05 seconds
TestRunner: sco-tester PASS 8.93 seconds
TestRunner: smp-tester PASS 8.91 seconds
TestRunner: userchan-tester PASS 5.92 seconds
Details
##############################
Test: CheckPatch - FAIL - 1.75 seconds
Run checkpatch.pl script with rule in .checkpatch.conf
Bluetooth: Add default wakeup callback for HCI UART driver\ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit fatal: unsaf ("ace/src' is owned by someone else)")'
#82:
callback since 'commit 4539ca67fe8e ("Bluetooth: Rename driver
.prevent_wake to .wakeup")'. This patch adds a default wakeup callback
total: 1 errors, 0 warnings, 23 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/12905037.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:[~2022-07-04 11:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 10:33 [PATCH] Bluetooth: Add default wakeup callback for HCI UART driver Ying Hsu
2022-07-04 11:07 ` bluez.test.bot [this message]
2022-07-20 16:20 ` patchwork-bot+bluetooth
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=62c2c9d6.1c69fb81.9177.d9be@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=yinghsu@chromium.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).