From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, hildawu@realtek.com
Subject: RE: [RESEND,v7] Bluetooth: btrtl: Add firmware format v3 support
Date: Tue, 08 Sep 2026 08:54:47 -0700 (PDT) [thread overview]
Message-ID: <6aa02fc7.8d510ab8.195d0.d724@mx.google.com> (raw)
In-Reply-To: <20260908075517.661675-1-hildawu@realtek.com>
[-- Attachment #1: Type: text/plain, Size: 5599 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/series/1160249/
---Test result---
Test Summary:
CheckPatch FAIL 2.44 seconds
VerifyFixes PASS 0.12 seconds
VerifySignedoff PASS 0.13 seconds
GitLint FAIL 0.32 seconds
SubjectPrefix PASS 0.11 seconds
BuildKernel PASS 26.64 seconds
CheckAllWarning PASS 29.72 seconds
CheckSparse PASS 27.79 seconds
BuildKernel32 PASS 25.69 seconds
CheckKernelLLVM SKIP 0.00 seconds
TestRunnerSetup PASS 474.85 seconds
IncrementalBuild PASS 26.04 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[RESEND,v7] Bluetooth: btrtl: Add firmware format v3 support
WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
#839:
new file mode 100644
total: 0 errors, 1 warnings, 1425 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/14798218.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:
[RESEND,v7] Bluetooth: btrtl: Add firmware format v3 support
21: B1 Line exceeds max length (85>80): "[ 1.838104] Bluetooth: btrtl_read_chip_id() hci0: RTL: chip_id status=0x00 id=0x3e"
22: B1 Line exceeds max length (116>80): "[ 1.838331] Bluetooth: btrtl_initialize() hci0: RTL: examining hci_ver=0e hci_rev=000d lmp_ver=0e lmp_subver=8922"
23: B1 Line exceeds max length (90>80): "[ 1.838571] Bluetooth: rtl_read_rom_version() hci0: RTL: rom_version status=0 version=0"
24: B1 Line exceeds max length (82>80): "[ 1.838821] Bluetooth: btrtl_initialize() hci0: RTL: btrtl_initialize: key id 0"
25: B1 Line exceeds max length (84>80): "[ 1.838825] Bluetooth: rtl_load_file() hci0: RTL: loading rtl_bt/rtl8922du_fw.bin"
26: B1 Line exceeds max length (88>80): "[ 1.843021] Bluetooth: rtl_load_file() hci0: RTL: loading rtl_bt/rtl8922du_config.bin"
28: B1 Line exceeds max length (118>80): "[ 1.843325] Bluetooth: rtlbt_parse_section_v3() hci0: RTL: subsection (f000:00), chip id 62, cut 0x01, len 0000c704"
29: B1 Line exceeds max length (90>80): "[ 1.843342] Bluetooth: rtlbt_parse_section_v3() hci0: RTL: subsection version: c5900782"
30: B1 Line exceeds max length (103>80): "[ 1.843347] Bluetooth: rtlbt_parse_config() hci0: RTL: config file: rtl_bt/rtl8922du_config_f000.bin"
31: B1 Line exceeds max length (126>80): "[ 1.843363] Bluetooth: rtlbt_parse_config() hci0: RTL: config file: rtl_bt/rtl8922du_config_f000.bin not found, use default"
32: B1 Line exceeds max length (118>80): "[ 1.843366] Bluetooth: rtlbt_parse_section_v3() hci0: RTL: subsection (f002:00), chip id 62, cut 0x01, len 00034378"
33: B1 Line exceeds max length (90>80): "[ 1.843417] Bluetooth: rtlbt_parse_section_v3() hci0: RTL: subsection version: 2b84a8b2"
34: B1 Line exceeds max length (103>80): "[ 1.843421] Bluetooth: rtlbt_parse_config() hci0: RTL: config file: rtl_bt/rtl8922du_config_f002.bin"
35: B1 Line exceeds max length (109>80): "[ 1.843647] Bluetooth: rtlbt_parse_config() hci0: RTL: config file: rtl_bt/rtl8922du_config_f002.bin found"
36: B1 Line exceeds max length (118>80): "[ 1.843654] Bluetooth: rtlbt_parse_section_v3() hci0: RTL: subsection (f000:00), chip id 62, cut 0x01, len 0000c704"
37: B1 Line exceeds max length (90>80): "[ 1.843658] Bluetooth: rtlbt_parse_section_v3() hci0: RTL: skip, key_id mismatch (1, 0)"
38: B1 Line exceeds max length (118>80): "[ 1.843661] Bluetooth: rtlbt_parse_section_v3() hci0: RTL: subsection (f002:00), chip id 62, cut 0x01, len 00034378"
39: B1 Line exceeds max length (90>80): "[ 1.843664] Bluetooth: rtlbt_parse_section_v3() hci0: RTL: skip, key_id mismatch (1, 0)"
40: B1 Line exceeds max length (118>80): "[ 1.843672] Bluetooth: rtlbt_parse_section_v3() hci0: RTL: subsection (f000:00), chip id 62, cut 0x01, len 0000c704"
41: B1 Line exceeds max length (90>80): "[ 1.843674] Bluetooth: rtlbt_parse_section_v3() hci0: RTL: skip, key_id mismatch (2, 0)"
42: B1 Line exceeds max length (118>80): "[ 1.843676] Bluetooth: rtlbt_parse_section_v3() hci0: RTL: subsection (f002:00), chip id 62, cut 0x01, len 00034378"
43: B1 Line exceeds max length (90>80): "[ 1.843678] Bluetooth: rtlbt_parse_section_v3() hci0: RTL: skip, key_id mismatch (2, 0)"
44: B1 Line exceeds max length (109>80): "[ 1.843680] Bluetooth: rtlbt_parse_firmware_v3() hci0: RTL: firmware section payload total len: 0x00040a7c"
45: B1 Line exceeds max length (85>80): "[ 2.293192] Bluetooth: rtl_finalize_download() hci0: RTL: Watchdog reset status 00"
46: B1 Line exceeds max length (82>80): "[ 2.293957] Bluetooth: rtl_finalize_download() hci0: RTL: fw version 0x2b84a8b2"
##############################
Test: CheckKernelLLVM - SKIP
Desc: Build kernel with LLVM + context analysis
Output:
Clang not found
https://github.com/bluez/bluetooth-next/pull/720
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-09-08 15:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 7:55 [RESEND PATCH v7] Bluetooth: btrtl: Add firmware format v3 support Hilda Wu
2026-09-08 15:54 ` bluez.test.bot [this message]
2026-09-08 16:19 ` Luiz Augusto von Dentz
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=6aa02fc7.8d510ab8.195d0.d724@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=hildawu@realtek.com \
--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