From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, ismael@iodev.co.uk
Subject: RE: Bluetooth: hci_sync: Fix opcode format in debug message
Date: Sun, 24 Jul 2022 15:03:20 -0700 (PDT) [thread overview]
Message-ID: <62ddc1a8.1c69fb81.f40b3.5478@mx.google.com> (raw)
In-Reply-To: <20220724212639.29269-1-ismael@iodev.co.uk>
[-- Attachment #1: Type: text/plain, Size: 1809 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=662601
---Test result---
Test Summary:
CheckPatch FAIL 1.37 seconds
GitLint PASS 0.83 seconds
SubjectPrefix PASS 0.62 seconds
BuildKernel PASS 37.10 seconds
BuildKernel32 PASS 32.02 seconds
Incremental Build with patchesPASS 49.05 seconds
TestRunner: Setup PASS 536.08 seconds
TestRunner: l2cap-tester PASS 16.75 seconds
TestRunner: bnep-tester PASS 6.11 seconds
TestRunner: mgmt-tester PASS 99.35 seconds
TestRunner: rfcomm-tester PASS 9.41 seconds
TestRunner: sco-tester PASS 9.12 seconds
TestRunner: smp-tester PASS 9.25 seconds
TestRunner: userchan-tester PASS 6.28 seconds
Details
##############################
Test: CheckPatch - FAIL - 1.37 seconds
Run checkpatch.pl script with rule in .checkpatch.conf
Bluetooth: hci_sync: Fix opcode format in debug message\WARNING:COMMIT_MESSAGE: Missing commit description - Add an appropriate one
total: 0 errors, 1 warnings, 0 checks, 8 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/12927635.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-24 22:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-24 21:26 [PATCH] Bluetooth: hci_sync: Fix opcode format in debug message Ismael Luceno
2022-07-24 22:03 ` bluez.test.bot [this message]
2022-07-26 18:58 ` 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=62ddc1a8.1c69fb81.f40b3.5478@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=ismael@iodev.co.uk \
--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