From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, zzzccc427@gmail.com
Subject: RE: Bluetooth: SMP: Serialize root channel updates
Date: Wed, 18 Nov 2026 02:07:11 -0800 (PST) [thread overview]
Message-ID: <6afd78cf.bdce4de1.73551.5c01@mx.google.com> (raw)
In-Reply-To: <pm-bluetooth-objects-candidate-0184-v11-900043ed2303656c76fe-1@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4461 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/1214536/
---Test result---
Test Summary:
CheckPatch FAIL 3.40 seconds
VerifyFixes PASS 0.08 seconds
VerifySignedoff PASS 0.07 seconds
GitLint PASS 0.94 seconds
SubjectPrefix PASS 0.28 seconds
BuildKernel PASS 31.22 seconds
CheckAllWarning PASS 35.87 seconds
CheckSparse PASS 38.39 seconds
BuildKernel32 PASS 30.97 seconds
CheckKernelLLVM PASS 34.86 seconds
TestRunnerSetup PASS 754.06 seconds
TestRunner_l2cap-tester PASS 14.77 seconds
TestRunner_iso-tester PASS 13.28 seconds
TestRunner_bnep-tester PASS 3.14 seconds
TestRunner_mgmt-tester PASS 87.96 seconds
TestRunner_rfcomm-tester PASS 4.46 seconds
TestRunner_sco-tester PASS 5.63 seconds
TestRunner_ioctl-tester PASS 4.66 seconds
TestRunner_mesh-tester PASS 5.55 seconds
TestRunner_smp-tester PASS 4.35 seconds
TestRunner_userchan-tester PASS 3.22 seconds
TestRunner_6lowpan-tester PASS 4.40 seconds
IncrementalBuild PASS 40.84 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[v4,1/4] Bluetooth: SMP: Publish root channels after initialization
WARNING: Non-standard signature: Assisted-by:
#149:
Assisted-by: LLM
ERROR: Unrecognized email address: 'LLM'
#149:
Assisted-by: LLM
total: 1 errors, 1 warnings, 0 checks, 36 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.
/home/runner/work/bluetooth-next/bluetooth-next/src/patch/14995467.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.
[v4,2/4] Bluetooth: SMP: Serialize forced BR/EDR channel changes
WARNING: Non-standard signature: Assisted-by:
#225:
Assisted-by: LLM
ERROR: Unrecognized email address: 'LLM'
#225:
Assisted-by: LLM
total: 1 errors, 1 warnings, 0 checks, 43 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.
/home/runner/work/bluetooth-next/bluetooth-next/src/patch/14995468.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.
[v4,3/4] Bluetooth: hci_core: Hold the request lock for the power-on update
WARNING: Non-standard signature: Assisted-by:
#158:
Assisted-by: LLM
ERROR: Unrecognized email address: 'LLM'
#158:
Assisted-by: LLM
total: 1 errors, 1 warnings, 0 checks, 17 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.
/home/runner/work/bluetooth-next/bluetooth-next/src/patch/14995469.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.
[v4,4/4] Bluetooth: SMP: Serialize root channel replacement
WARNING: Non-standard signature: Assisted-by:
#323:
Assisted-by: LLM
ERROR: Unrecognized email address: 'LLM'
#323:
Assisted-by: LLM
total: 1 errors, 1 warnings, 0 checks, 48 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.
/home/runner/work/bluetooth-next/bluetooth-next/src/patch/14995470.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.
https://github.com/bluez/bluetooth-next/pull/1147
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-11-18 10:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-18 4:21 [PATCH v4 0/4] Bluetooth: SMP: Serialize root channel updates Cen Zhang
2026-11-18 4:21 ` [PATCH v4 1/4] Bluetooth: SMP: Publish root channels after initialization Cen Zhang
2026-11-18 10:07 ` bluez.test.bot [this message]
2026-11-18 4:21 ` [PATCH v4 2/4] Bluetooth: SMP: Serialize forced BR/EDR channel changes Cen Zhang
2026-11-18 4:21 ` [PATCH v4 3/4] Bluetooth: hci_core: Hold the request lock for the power-on update Cen Zhang
2026-11-18 4:21 ` [PATCH v4 4/4] Bluetooth: SMP: Serialize root channel replacement Cen Zhang
-- strict thread matches above, loose matches on Subject: below --
2026-10-31 7:32 [PATCH v3 1/3] Bluetooth: SMP: Serialize forced BR/EDR channel changes Cen Zhang
2026-10-31 9:44 ` Bluetooth: SMP: Serialize root channel updates bluez.test.bot
2026-10-30 14:43 [PATCH 1/2] Bluetooth: SMP: Serialize forced BR/EDR channel changes Cen Zhang
2026-10-30 16:41 ` Bluetooth: SMP: Serialize root channel updates 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=6afd78cf.bdce4de1.73551.5c01@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=zzzccc427@gmail.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