public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, devnull+yang.li.amlogic.com@kernel.org
Subject: RE: Add support for Amlogic HCI UART
Date: Fri, 02 Aug 2024 03:36:44 -0700 (PDT)	[thread overview]
Message-ID: <66acb6bc.050a0220.87ed5.2e41@mx.google.com> (raw)
In-Reply-To: <20240802-btaml-v3-1-d8110bf9963f@amlogic.com>

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

---Test result---

Test Summary:
CheckPatch                    FAIL      3.83 seconds
GitLint                       PASS      1.01 seconds
SubjectPrefix                 FAIL      0.63 seconds
BuildKernel                   PASS      29.87 seconds
CheckAllWarning               PASS      32.17 seconds
CheckSparse                   PASS      37.72 seconds
CheckSmatch                   PASS      104.87 seconds
BuildKernel32                 PASS      28.88 seconds
TestRunnerSetup               PASS      527.54 seconds
TestRunner_l2cap-tester       PASS      20.20 seconds
TestRunner_iso-tester         PASS      37.42 seconds
TestRunner_bnep-tester        PASS      5.01 seconds
TestRunner_mgmt-tester        PASS      121.51 seconds
TestRunner_rfcomm-tester      PASS      29.14 seconds
TestRunner_sco-tester         PASS      43.15 seconds
TestRunner_ioctl-tester       PASS      7.97 seconds
TestRunner_mesh-tester        PASS      8.22 seconds
TestRunner_smp-tester         PASS      6.98 seconds
TestRunner_userchan-tester    PASS      5.09 seconds
IncrementalBuild              PASS      40.27 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[v3,1/3] dt-bindings: net: bluetooth: Add support for Amlogic Bluetooth
WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
#93: 
new file mode 100644

total: 0 errors, 1 warnings, 62 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/13751350.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.


[v3,2/3] Bluetooth: hci_uart: Add support for Amlogic HCI UART
WARNING: please write a help paragraph that fully describes the config symbol
#108: FILE: drivers/bluetooth/Kconfig:277:
+config BT_HCIUART_AML
+	bool "Amlogic protocol support"
+	depends on BT_HCIUART
+	depends on BT_HCIUART_SERDEV
+	select BT_HCIUART_H4
+	select FW_LOADER
+	help
+	  The Amlogic protocol support enables Bluetooth HCI over serial
+	  port interface for Amlogic Bluetooth controllers.
+
+	  Say Y here to compile support for HCI AML protocol.
+

WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
#134: 
new file mode 100644

total: 0 errors, 2 warnings, 822 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/13751352.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


  reply	other threads:[~2024-08-02 10:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-02  9:39 [PATCH v3 0/3] Add support for Amlogic HCI UART Yang Li via B4 Relay
2024-08-02  9:39 ` [PATCH v3 1/3] dt-bindings: net: bluetooth: Add support for Amlogic Bluetooth Yang Li via B4 Relay
2024-08-02 10:36   ` bluez.test.bot [this message]
2024-08-05 17:27   ` Krzysztof Kozlowski
2024-08-06  6:54     ` Yang Li
2024-08-02  9:39 ` [PATCH v3 2/3] Bluetooth: hci_uart: Add support for Amlogic HCI UART Yang Li via B4 Relay
2024-08-02 11:02   ` Paul Menzel
2024-08-06  6:27     ` Yang Li
2024-08-05 17:29   ` Krzysztof Kozlowski
2024-08-06  8:33     ` Yang Li
2024-08-06  8:37       ` Krzysztof Kozlowski
2024-08-02  9:39 ` [PATCH v3 3/3] MAINTAINERS: Add an entry for Amlogic HCI UART (M: Yang Li) Yang Li via B4 Relay
  -- strict thread matches above, loose matches on Subject: below --
2024-08-09  5:42 [PATCH v4 1/3] dt-bindings: net: bluetooth: Add support for Amlogic Bluetooth Yang Li via B4 Relay
2024-08-09  6:40 ` Add support for Amlogic HCI UART bluez.test.bot
2024-07-18  7:42 [PATCH v2 1/3] dt-bindings: net: bluetooth: Add support for Amlogic Bluetooth Yang Li via B4 Relay
2024-07-18  8:38 ` Add support for Amlogic HCI UART bluez.test.bot
2024-07-05 11:20 [PATCH 1/4] dt-bindings: net: bluetooth: Add support for Amlogic Bluetooth Yang Li via B4 Relay
2024-07-05 11:57 ` Add support for Amlogic HCI UART 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=66acb6bc.050a0220.87ed5.2e41@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=devnull+yang.li.amlogic.com@kernel.org \
    --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