From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, Larry.Finger@lwfinger.net
Subject: RE: bluetooth: Add device 0bda:4853 to device tables
Date: Tue, 08 Aug 2023 14:04:57 -0700 (PDT) [thread overview]
Message-ID: <64d2adf9.170a0220.cd28b.4701@mx.google.com> (raw)
In-Reply-To: <20230808193455.11037-1-Larry.Finger@lwfinger.net>
[-- Attachment #1: Type: text/plain, Size: 2358 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=774260
---Test result---
Test Summary:
CheckPatch FAIL 0.91 seconds
GitLint PASS 0.25 seconds
SubjectPrefix FAIL 0.38 seconds
BuildKernel PASS 39.26 seconds
CheckAllWarning PASS 42.74 seconds
CheckSparse PASS 48.08 seconds
CheckSmatch PASS 130.45 seconds
BuildKernel32 PASS 38.65 seconds
TestRunnerSetup PASS 577.23 seconds
TestRunner_l2cap-tester PASS 27.36 seconds
TestRunner_iso-tester PASS 64.60 seconds
TestRunner_bnep-tester PASS 12.57 seconds
TestRunner_mgmt-tester PASS 244.50 seconds
TestRunner_rfcomm-tester PASS 18.59 seconds
TestRunner_sco-tester PASS 21.44 seconds
TestRunner_ioctl-tester PASS 20.93 seconds
TestRunner_mesh-tester PASS 15.54 seconds
TestRunner_smp-tester PASS 16.46 seconds
TestRunner_userchan-tester PASS 13.01 seconds
IncrementalBuild PASS 35.29 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
bluetooth: Add device 0bda:4853 to device tables
WARNING: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#82:
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/13346977.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
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2023-08-08 21:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 19:34 [PATCH] bluetooth: Add device 0bda:4853 to device tables Larry Finger
2023-08-08 21:04 ` bluez.test.bot [this message]
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=64d2adf9.170a0220.cd28b.4701@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