From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, loic.poulain@oss.qualcomm.com
Subject: RE: Support for block device NVMEM providers
Date: Thu, 30 Jul 2026 10:30:23 -0700 (PDT) [thread overview]
Message-ID: <6a6b8a2f.21a19891.1e44db.9f64@mx.google.com> (raw)
In-Reply-To: <20260730-block-as-nvmem-v9-1-f72935817dbf@oss.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 4150 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=1137570
---Test result---
Test Summary:
CheckPatch FAIL 7.82 seconds
VerifyFixes PASS 0.09 seconds
VerifySignedoff PASS 0.09 seconds
GitLint FAIL 2.32 seconds
SubjectPrefix FAIL 0.82 seconds
BuildKernel PASS 24.20 seconds
CheckAllWarning PASS 27.02 seconds
CheckSparse PASS 26.03 seconds
BuildKernel32 PASS 23.83 seconds
CheckKernelLLVM SKIP 0.00 seconds
TestRunnerSetup PASS 441.18 seconds
TestRunner_l2cap-tester PASS 64.99 seconds
TestRunner_iso-tester PASS 92.37 seconds
TestRunner_bnep-tester PASS 18.91 seconds
TestRunner_mgmt-tester FAIL 233.05 seconds
TestRunner_rfcomm-tester PASS 25.34 seconds
TestRunner_sco-tester PASS 31.47 seconds
TestRunner_ioctl-tester PASS 26.19 seconds
TestRunner_mesh-tester FAIL 24.81 seconds
TestRunner_smp-tester PASS 23.26 seconds
TestRunner_userchan-tester PASS 19.52 seconds
TestRunner_6lowpan-tester PASS 22.78 seconds
IncrementalBuild PASS 68.30 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[v9,06/10] block: implement NVMEM provider
WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
#241:
new file mode 100644
total: 0 errors, 1 warnings, 186 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/patch/14721276.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: GitLint - FAIL
Desc: Run gitlint
Output:
[v9,10/10] arm64: dts: qcom: arduino-imola: Describe NVMEM layout for WiFi/BT addresses
1: T1 Title exceeds max length (87>80): "[v9,10/10] arm64: dts: qcom: arduino-imola: Describe NVMEM layout for WiFi/BT addresses"
##############################
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
"Bluetooth: " prefix is not specified in the subject
"Bluetooth: " prefix is not specified in the subject
"Bluetooth: " prefix is not specified in the subject
"Bluetooth: " prefix is not specified in the subject
"Bluetooth: " prefix is not specified in the subject
"Bluetooth: " prefix is not specified in the subject
##############################
Test: CheckKernelLLVM - SKIP
Desc: Build kernel with LLVM + context analysis
Output:
Clang not found
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 501, Passed: 487 (97.2%), Failed: 4, Not Run: 10
Failed Test Cases
Set Low Energy on 6.2 - SCI Setting Failed 0.379 seconds
Read Exp Feature - Success Failed 0.271 seconds
LL Privacy - Unpair 1 Timed out 2.043 seconds
LL Privacy - Unpair 2 (Remove from AL) Timed out 4.930 seconds
##############################
Test: TestRunner_mesh-tester - FAIL
Desc: Run mesh-tester with test-runner
Output:
Total: 10, Passed: 8 (80.0%), Failed: 2, Not Run: 0
Failed Test Cases
Mesh - Send cancel - 1 Timed out 1.849 seconds
Mesh - Send cancel - 2 Timed out 1.990 seconds
https://github.com/bluez/bluetooth-next/pull/518
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-07-30 17:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 16:00 [PATCH v9 00/10] Support for block device NVMEM providers Loic Poulain
2026-07-30 16:00 ` [PATCH v9 01/10] dt-bindings: mmc: Document fixed-layout NVMEM provider support Loic Poulain
2026-07-30 17:30 ` bluez.test.bot [this message]
2026-07-30 16:00 ` [PATCH v9 02/10] dt-bindings: net: wireless: qcom,ath10k: Document NVMEM cells Loic Poulain
2026-07-30 16:00 ` [PATCH v9 03/10] dt-bindings: bluetooth: qcom: Add NVMEM BD address cell Loic Poulain
2026-07-30 16:00 ` [PATCH v9 04/10] nvmem: layouts: Support fixed-layout as the nvmem device node itself Loic Poulain
2026-07-30 16:00 ` [PATCH v9 05/10] block: partitions: of: Attach partition fwnode to the block device Loic Poulain
2026-07-30 16:00 ` [PATCH v9 06/10] block: implement NVMEM provider Loic Poulain
2026-07-30 16:00 ` [PATCH v9 07/10] net: of_net: Add of_get_nvmem_eui48() helper for EUI-48 lookup Loic Poulain
2026-07-30 16:00 ` [PATCH v9 08/10] Bluetooth: hci_sync: Add NVMEM-backed BD address retrieval Loic Poulain
2026-07-30 16:00 ` [PATCH v9 09/10] Bluetooth: qca: Set NVMEM BD address quirks when address is invalid Loic Poulain
2026-07-30 16:00 ` [PATCH v9 10/10] arm64: dts: qcom: arduino-imola: Describe NVMEM layout for WiFi/BT addresses Loic Poulain
-- strict thread matches above, loose matches on Subject: below --
2026-07-03 13:45 [PATCH v8 1/9] dt-bindings: mmc: Document fixed-layout NVMEM provider support Loic Poulain
2026-07-03 16:12 ` Support for block device NVMEM providers bluez.test.bot
2026-07-01 16:00 [PATCH v7 1/9] dt-bindings: mmc: Document fixed-layout NVMEM provider support Loic Poulain
2026-07-01 17:01 ` Support for block device NVMEM providers bluez.test.bot
2026-06-29 8:55 [PATCH v6 1/9] block: partitions: of: Skip child nodes without reg property Loic Poulain
2026-06-29 12:30 ` Support for block device NVMEM providers bluez.test.bot
2026-06-12 13:20 [PATCH v5 1/9] block: partitions: of: Skip child nodes without reg property Loic Poulain
2026-06-12 16:24 ` Support for block device NVMEM providers bluez.test.bot
2026-06-09 7:52 [PATCH v4 1/8] dt-bindings: mmc: Document support for nvmem-layout Loic Poulain
2026-06-09 9:31 ` Support for block device NVMEM providers bluez.test.bot
2026-06-08 10:50 [PATCH v3 1/7] dt-bindings: mmc: Document support for nvmem-layout Loic Poulain
2026-06-08 12:12 ` Support for block device NVMEM providers bluez.test.bot
2026-05-07 15:24 [PATCH v2 1/8] dt-bindings: mmc: Document support for nvmem-layout Loic Poulain
2026-05-07 16:19 ` Support for block device NVMEM providers bluez.test.bot
2026-04-28 14:23 [PATCH 1/9] dt-bindings: mmc: Document support for nvmem-layout Loic Poulain
2026-04-28 17:44 ` Support for block device NVMEM providers 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=6a6b8a2f.21a19891.1e44db.9f64@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=loic.poulain@oss.qualcomm.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