From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, neeraj.sanjaykale@nxp.com
Subject: RE: Add support for NXP bluetooth chipsets
Date: Thu, 23 Feb 2023 03:01:04 -0800 (PST) [thread overview]
Message-ID: <63f74770.4a0a0220.16b18.d666@mx.google.com> (raw)
In-Reply-To: <20230223103614.4137309-2-neeraj.sanjaykale@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 2228 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=724310
---Test result---
Test Summary:
CheckPatch PASS 1.75 seconds
GitLint FAIL 0.90 seconds
SubjectPrefix FAIL 0.60 seconds
BuildKernel PASS 31.48 seconds
CheckAllWarning PASS 35.04 seconds
CheckSparse PASS 39.71 seconds
CheckSmatch PASS 107.50 seconds
BuildKernel32 PASS 30.82 seconds
TestRunnerSetup PASS 441.27 seconds
TestRunner_l2cap-tester PASS 16.52 seconds
TestRunner_iso-tester PASS 17.22 seconds
TestRunner_bnep-tester PASS 5.70 seconds
TestRunner_mgmt-tester PASS 112.84 seconds
TestRunner_rfcomm-tester PASS 9.16 seconds
TestRunner_sco-tester PASS 8.41 seconds
TestRunner_ioctl-tester PASS 9.76 seconds
TestRunner_mesh-tester PASS 7.23 seconds
TestRunner_smp-tester PASS 8.24 seconds
TestRunner_userchan-tester PASS 6.02 seconds
IncrementalBuild PASS 32.75 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[v5,2/3] dt-bindings: net: Bluetooth: Add NXP bluetooth support
WARNING: I3 - ignore-body-lines: gitlint will be switching from using Python regex 'match' (match beginning) to 'search' (match anywhere) semantics. Please review your ignore-body-lines.regex option accordingly. To remove this warning, set general.regex-style-search=True. More details: https://jorisroovers.github.io/gitlint/configuration/#regex-style-search
18: B1 Line exceeds max length (87>80): " create mode 100644 Documentation/devicetree/bindings/net/bluetooth/nxp,88w8987-bt.yaml"
##############################
Test: SubjectPrefix - FAIL
Desc: Check subject contains "Bluetooth" prefix
Output:
"Bluetooth: " prefix is not specified in the subject
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-02-23 11:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 10:36 [PATCH v5 0/3] Add support for NXP bluetooth chipsets Neeraj Sanjay Kale
2023-02-23 10:36 ` [PATCH v5 1/3] serdev: Add method to assert break signal over tty UART port Neeraj Sanjay Kale
2023-02-23 11:01 ` bluez.test.bot [this message]
2023-02-23 10:36 ` [PATCH v5 2/3] dt-bindings: net: Bluetooth: Add NXP bluetooth support Neeraj Sanjay Kale
2023-02-24 11:20 ` Krzysztof Kozlowski
2023-02-23 10:36 ` [PATCH v5] Bluetooth: NXP: Add protocol support for NXP Bluetooth chipsets Neeraj Sanjay Kale
2023-02-23 10:41 ` [v5] " bluez.test.bot
2023-02-23 10:48 ` [PATCH v5] " Greg KH
2023-02-23 13:57 ` Neeraj sanjay kale
2023-02-23 14:02 ` Greg KH
2023-02-23 14:06 ` Neeraj sanjay kale
2023-02-23 11:32 ` Sherry Sun
2023-03-01 15:51 ` Neeraj sanjay kale
-- strict thread matches above, loose matches on Subject: below --
2023-03-16 17:22 [PATCH v13 1/4] serdev: Replace all instances of ENOTSUPP with EOPNOTSUPP Neeraj Sanjay Kale
2023-03-16 18:36 ` Add support for NXP bluetooth chipsets bluez.test.bot
2023-03-15 12:03 [PATCH v12 1/4] serdev: Replace all instances of ENOTSUPP with EOPNOTSUPP Neeraj Sanjay Kale
2023-03-15 12:42 ` Add support for NXP bluetooth chipsets bluez.test.bot
2023-03-14 15:32 [PATCH v11 1/4] serdev: Replace all instances of ENOTSUPP with EOPNOTSUPP Neeraj Sanjay Kale
2023-03-14 16:03 ` Add support for NXP bluetooth chipsets bluez.test.bot
2023-03-13 14:40 [PATCH v10 1/3] serdev: Add method to assert break signal over tty UART port Neeraj Sanjay Kale
2023-03-13 15:33 ` Add support for NXP bluetooth chipsets bluez.test.bot
2023-03-13 14:09 [PATCH v9 1/3] serdev: Add method to assert break signal over tty UART port Neeraj Sanjay Kale
2023-03-13 14:33 ` Add support for NXP bluetooth chipsets bluez.test.bot
2023-03-10 18:19 [PATCH v8 1/3] serdev: Add method to assert break signal over tty UART port Neeraj Sanjay Kale
2023-03-10 19:03 ` Add support for NXP bluetooth chipsets bluez.test.bot
2023-03-06 17:05 [PATCH v7 1/3] serdev: Add method to assert break signal over tty UART port Neeraj Sanjay Kale
2023-03-06 17:33 ` Add support for NXP bluetooth chipsets bluez.test.bot
2023-03-01 15:45 [PATCH v6 1/3] serdev: Add method to assert break signal over tty UART port Neeraj Sanjay Kale
2023-03-01 16:38 ` Add support for NXP bluetooth chipsets bluez.test.bot
2023-02-21 16:25 [PATCH v4 1/3] serdev: Add method to assert break signal over tty UART port Neeraj Sanjay Kale
2023-02-21 17:10 ` Add support for NXP bluetooth chipsets bluez.test.bot
2023-02-13 14:54 [PATCH v3 1/3] serdev: Add method to assert break signal over tty UART port Neeraj Sanjay Kale
2023-02-13 15:40 ` Add support for NXP bluetooth chipsets bluez.test.bot
2023-01-30 18:05 [PATCH v2 1/3] serdev: Add method to assert break Neeraj Sanjay Kale
2023-01-30 18:35 ` Add support for NXP bluetooth chipsets bluez.test.bot
2023-01-24 17:47 [PATCH v1 1/3] serdev: Add method to assert break Neeraj Sanjay Kale
2023-01-24 18:38 ` Add support for NXP bluetooth chipsets 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=63f74770.4a0a0220.16b18.d666@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=neeraj.sanjaykale@nxp.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.