From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, macroalpha82@gmail.com
Subject: RE: Bluetooth: Add support for RTL8821CS
Date: Thu, 26 Jan 2023 09:35:42 -0800 (PST) [thread overview]
Message-ID: <63d2b9ee.e90a0220.863c.3f4c@mx.google.com> (raw)
In-Reply-To: <20230126165529.1452252-2-macroalpha82@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2047 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=715934
---Test result---
Test Summary:
CheckPatch PASS 2.17 seconds
GitLint PASS 0.75 seconds
SubjectPrefix FAIL 0.58 seconds
BuildKernel PASS 38.49 seconds
CheckAllWarning PASS 41.50 seconds
CheckSparse WARNING 47.05 seconds
CheckSmatch WARNING 127.35 seconds
BuildKernel32 PASS 36.70 seconds
TestRunnerSetup PASS 526.86 seconds
TestRunner_l2cap-tester PASS 19.05 seconds
TestRunner_iso-tester PASS 20.75 seconds
TestRunner_bnep-tester PASS 6.80 seconds
TestRunner_mgmt-tester PASS 129.94 seconds
TestRunner_rfcomm-tester PASS 10.75 seconds
TestRunner_sco-tester PASS 9.87 seconds
TestRunner_ioctl-tester PASS 11.82 seconds
TestRunner_mesh-tester PASS 8.72 seconds
TestRunner_smp-tester PASS 9.75 seconds
TestRunner_userchan-tester PASS 7.21 seconds
IncrementalBuild PASS 40.32 seconds
Details
##############################
Test: SubjectPrefix - FAIL
Desc: Check subject contains "Bluetooth" prefix
Output:
"Bluetooth: " prefix is not specified in the subject
##############################
Test: CheckSparse - WARNING
Desc: Run sparse tool with linux kernel
Output:
drivers/bluetooth/btrtl.c: note: in included file:drivers/bluetooth/btrtl.h:47:45: warning: array of flexible structures
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
drivers/bluetooth/btrtl.c: note: in included file:drivers/bluetooth/btrtl.h:47:45: warning: array of flexible structures
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-01-26 17:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 16:55 [PATCH RFC 0/2] Bluetooth: Add support for RTL8821CS Chris Morgan
2023-01-26 16:55 ` [PATCH RFC 1/2] dt-bindings: net: realtek-bluetooth: Add RTL8821CS Chris Morgan
2023-01-26 17:35 ` bluez.test.bot [this message]
2023-01-27 10:24 ` Krzysztof Kozlowski
2023-01-27 16:46 ` Chris Morgan
2023-01-27 16:53 ` Krzysztof Kozlowski
2023-01-27 17:00 ` Chris Morgan
2023-01-27 17:02 ` Krzysztof Kozlowski
2023-01-26 16:55 ` [PATCH RFC 2/2] Bluetooth: hci_h5: btrtl: Add support for RTL8821CS Chris Morgan
-- strict thread matches above, loose matches on Subject: below --
2023-02-24 23:23 [PATCH 1/3 V2] dt-bindings: net: realtek-bluetooth: Add RTL8821CS Chris Morgan
2023-02-24 23:57 ` Bluetooth: Add support for RTL8821CS bluez.test.bot
2023-02-27 16:30 [PATCH 1/3 V3] dt-bindings: net: realtek-bluetooth: Add RTL8821CS Chris Morgan
2023-02-27 17:09 ` Bluetooth: Add support for RTL8821CS bluez.test.bot
2023-02-28 15:22 [PATCH 1/3 V4] dt-bindings: net: realtek-bluetooth: Add RTL8821CS Chris Morgan
2023-02-28 15:59 ` Bluetooth: Add support for RTL8821CS bluez.test.bot
2023-03-15 17:36 [PATCH 1/3 V5] dt-bindings: net: realtek-bluetooth: Add RTL8821CS Chris Morgan
2023-03-15 17:39 ` Bluetooth: Add support for RTL8821CS bluez.test.bot
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=63d2b9ee.e90a0220.863c.3f4c@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=macroalpha82@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.