From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, Larry.Finger@lwfinger.net
Subject: RE: Bluetooth: Two additional devices
Date: Wed, 22 Mar 2023 19:30:58 -0700 (PDT) [thread overview]
Message-ID: <641bb9e2.050a0220.4989d.b63d@mx.google.com> (raw)
In-Reply-To: <20230323005203.19749-2-Larry.Finger@lwfinger.net>
[-- Attachment #1: Type: text/plain, Size: 2413 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=732932
---Test result---
Test Summary:
CheckPatch FAIL 1.81 seconds
GitLint PASS 0.64 seconds
SubjectPrefix FAIL 0.47 seconds
BuildKernel PASS 41.73 seconds
CheckAllWarning PASS 46.79 seconds
CheckSparse PASS 51.99 seconds
CheckSmatch PASS 137.37 seconds
BuildKernel32 PASS 41.32 seconds
TestRunnerSetup PASS 577.92 seconds
TestRunner_l2cap-tester PASS 20.25 seconds
TestRunner_iso-tester PASS 21.83 seconds
TestRunner_bnep-tester PASS 7.02 seconds
TestRunner_mgmt-tester PASS 132.10 seconds
TestRunner_rfcomm-tester PASS 11.65 seconds
TestRunner_sco-tester PASS 10.87 seconds
TestRunner_ioctl-tester PASS 11.96 seconds
TestRunner_mesh-tester PASS 8.82 seconds
TestRunner_smp-tester PASS 9.52 seconds
TestRunner_userchan-tester PASS 6.91 seconds
IncrementalBuild PASS 45.16 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[2/2] bluetooth: Add device 13d3:3571 to device tables
WARNING: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#86:
This device is part of a Realtek RTW8852BE chip. The device table is as follows:
total: 0 errors, 1 warnings, 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/src/13184800.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
Desc: Check subject contains "Bluetooth" prefix
Output:
"Bluetooth: " prefix is not specified in the subject
"Bluetooth: " prefix is not specified in the subject
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-03-23 2:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 0:52 [PATCH 0/2] Bluetooth: Two additional devices Larry Finger
2023-03-23 0:52 ` [PATCH 1/2] bluetooth: Add device 0bda:887b to device tables Larry Finger
2023-03-23 2:30 ` bluez.test.bot [this message]
2023-03-23 0:52 ` [PATCH 2/2] bluetooth: Add device 13d3:3571 " Larry Finger
2023-03-23 17:45 ` [PATCH v2 0/2] Bluetooth: Two additional devices Larry Finger
2023-03-23 17:45 ` [PATCH v2 1/2] Bluetooth: Add device 0bda:887b to device tables Larry Finger
2023-03-23 18:35 ` [v2,1/2] " bluez.test.bot
2023-03-28 21:00 ` [PATCH v2 1/2] " patchwork-bot+bluetooth
2023-03-23 17:45 ` [PATCH 2/2] Bluetooth: Add device 13d3:3571 " Larry Finger
2023-03-23 18:16 ` [2/2] " bluez.test.bot
2023-03-28 21:00 ` [PATCH 2/2] " patchwork-bot+bluetooth
2023-03-28 21:00 ` [PATCH 0/2] Bluetooth: Two additional devices 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=641bb9e2.050a0220.4989d.b63d@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--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