linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, rudi@heitbaum.com
Subject: RE: Bluetooth: btrtl: Add support for RTL8822BS
Date: Sun, 14 May 2023 01:34:48 -0700 (PDT)	[thread overview]
Message-ID: <64609d28.ca0a0220.a2c28.2166@mx.google.com> (raw)
In-Reply-To: <20230514074731.70614-2-rudi@heitbaum.com>

[-- Attachment #1: Type: text/plain, Size: 2782 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=747318

---Test result---

Test Summary:
CheckPatch                    PASS      2.04 seconds
GitLint                       PASS      0.89 seconds
SubjectPrefix                 FAIL      0.60 seconds
BuildKernel                   PASS      32.50 seconds
CheckAllWarning               WARNING   35.62 seconds
CheckSparse                   WARNING   40.87 seconds
CheckSmatch                   WARNING   110.27 seconds
BuildKernel32                 PASS      31.83 seconds
TestRunnerSetup               PASS      457.47 seconds
TestRunner_l2cap-tester       PASS      17.22 seconds
TestRunner_iso-tester         PASS      21.84 seconds
TestRunner_bnep-tester        PASS      5.67 seconds
TestRunner_mgmt-tester        PASS      117.57 seconds
TestRunner_rfcomm-tester      PASS      9.11 seconds
TestRunner_sco-tester         PASS      8.41 seconds
TestRunner_ioctl-tester       PASS      9.88 seconds
TestRunner_mesh-tester        PASS      7.20 seconds
TestRunner_smp-tester         PASS      8.31 seconds
TestRunner_userchan-tester    PASS      6.02 seconds
IncrementalBuild              PASS      39.59 seconds

Details
##############################
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
##############################
Test: CheckAllWarning - WARNING
Desc: Run linux kernel with all warning enabled
Output:
drivers/bluetooth/btrtl.c: In function ‘btrtl_set_quirks’:drivers/bluetooth/btrtl.c:1194:3: warning: this statement may fall through [-Wimplicit-fallthrough=] 1194 |   set_bit(HCI_QUIRK_BROKEN_LOCAL_EXT_FEATURES_PAGE_2, &hdev->quirks);      |   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~drivers/bluetooth/btrtl.c:1195:2: note: here 1195 |  default:      |  ^~~~~~~
##############################
Test: CheckSparse - WARNING
Desc: Run sparse tool with linux kernel
Output:
drivers/bluetooth/btrtl.c: In function ‘btrtl_set_quirks’:drivers/bluetooth/btrtl.c:1194:3: warning: this statement may fall through [-Wimplicit-fallthrough=]drivers/bluetooth/btrtl.c:1195:2: note: here
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
drivers/bluetooth/btrtl.c: In function ‘btrtl_set_quirks’:drivers/bluetooth/btrtl.c:1194:3: warning: this statement may fall through [-Wimplicit-fallthrough=]drivers/bluetooth/btrtl.c:1195:2: note: here


---
Regards,
Linux Bluetooth


  reply	other threads:[~2023-05-14  8:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-14  7:47 [PATCH 0/3] Bluetooth: btrtl: Add support for RTL8822BS Rudi Heitbaum
2023-05-14  7:47 ` [PATCH 1/3] dt-bindings: net: realtek-bluetooth: Add RTL8822BS Rudi Heitbaum
2023-05-14  8:34   ` bluez.test.bot [this message]
2023-05-14  9:51   ` Krzysztof Kozlowski
2023-05-14  9:53   ` Krzysztof Kozlowski
2023-05-14  7:47 ` [PATCH 2/3] Bluetooth: btrtl: Add support for RTL8822BS UART Rudi Heitbaum
2023-05-14  8:15   ` Christophe JAILLET
2023-05-14  9:14   ` kernel test robot
2023-05-14  9:44   ` kernel test robot
2023-05-14 11:05   ` kernel test robot
2023-05-14  7:47 ` [PATCH 3/3] arm64: dts: allwinner: h6: tanix-tx6: Add compatible bluetooth Rudi Heitbaum
2023-05-14  9:55   ` 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=64609d28.ca0a0220.a2c28.2166@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=rudi@heitbaum.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).