From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, dominique.martinet@atmark-techno.com
Subject: RE: Add serdev support for hci h4
Date: Mon, 07 Nov 2022 23:15:57 -0800 (PST) [thread overview]
Message-ID: <636a022d.c80a0220.b75f.108e@mx.google.com> (raw)
In-Reply-To: <20221108055531.2176793-2-dominique.martinet@atmark-techno.com>
[-- Attachment #1: Type: text/plain, Size: 2230 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=693092
---Test result---
Test Summary:
CheckPatch FAIL 1.79 seconds
GitLint PASS 2.09 seconds
SubjectPrefix FAIL 1.79 seconds
BuildKernel PASS 34.54 seconds
BuildKernel32 PASS 30.74 seconds
Incremental Build with patchesPASS 55.10 seconds
TestRunner: Setup PASS 516.75 seconds
TestRunner: l2cap-tester PASS 17.74 seconds
TestRunner: iso-tester PASS 17.16 seconds
TestRunner: bnep-tester PASS 6.69 seconds
TestRunner: mgmt-tester PASS 107.68 seconds
TestRunner: rfcomm-tester PASS 10.57 seconds
TestRunner: sco-tester PASS 10.02 seconds
TestRunner: ioctl-tester PASS 11.47 seconds
TestRunner: mesh-tester PASS 8.17 seconds
TestRunner: smp-tester PASS 9.94 seconds
TestRunner: userchan-tester PASS 6.99 seconds
Details
##############################
Test: CheckPatch - FAIL - 1.79 seconds
Run checkpatch.pl script with rule in .checkpatch.conf
[RFC,1/2] dt-bindings: net: h4-bluetooth: add new bindings for hci_h4\WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#114:
new file mode 100644
total: 0 errors, 1 warnings, 49 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/13035921.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: SubjectPrefix - FAIL - 1.79 seconds
Check subject contains "Bluetooth" prefix
"Bluetooth: " is not specified in the subject
"Bluetooth: " is not specified in the subject
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-11-08 7:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 5:55 [RFC PATCH 0/2] Add serdev support for hci h4 Dominique Martinet
2022-11-08 5:55 ` [RFC PATCH 1/2] dt-bindings: net: h4-bluetooth: add new bindings for hci_h4 Dominique Martinet
2022-11-08 7:15 ` bluez.test.bot [this message]
2022-11-08 11:37 ` Krzysztof Kozlowski
2022-11-08 23:54 ` Dominique Martinet
2022-11-09 7:29 ` Dominique Martinet
2022-11-09 22:00 ` Rob Herring
2022-11-10 7:37 ` Dominique Martinet
2022-11-10 16:27 ` Rob Herring
2022-11-08 12:54 ` Rob Herring
2022-11-08 13:59 ` Rob Herring
2022-11-18 3:50 ` Add serdev support for hci h4 bluez.test.bot
2022-11-18 4:38 ` bluez.test.bot
2022-11-18 5:34 ` bluez.test.bot
2022-11-18 6:34 ` bluez.test.bot
2022-11-18 7:33 ` bluez.test.bot
2022-11-18 8:37 ` bluez.test.bot
2022-11-18 9:31 ` bluez.test.bot
2022-11-08 5:55 ` [RFC PATCH 2/2] bluetooth/hci_h4: add serdev support Dominique Martinet
2022-11-08 20:38 ` Andrew Lunn
2022-11-08 20:58 ` Krzysztof Kozlowski
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=636a022d.c80a0220.b75f.108e@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=dominique.martinet@atmark-techno.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