From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, weihong.guan@gmail.com
Subject: RE: Bluetooth: Advertising sets on a single-set controller
Date: Wed, 11 Nov 2026 10:21:24 -0800 (PST) [thread overview]
Message-ID: <6af4b224.b0b4b201.1d9e8.638a@mx.google.com> (raw)
In-Reply-To: <20261111165133.827594-2-weihong.guan@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4889 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/1208570/
---Test result---
Test Summary:
CheckPatch FAIL 8.49 seconds
VerifyFixes PASS 6.43 seconds
VerifySignedoff PASS 1.36 seconds
GitLint PASS 14.44 seconds
SubjectPrefix PASS 17.47 seconds
BuildKernel PASS 23.98 seconds
CheckAllWarning PASS 27.11 seconds
CheckSparse WARNING 29.23 seconds
BuildKernel32 PASS 24.75 seconds
CheckKernelLLVM PASS 26.34 seconds
TestRunnerSetup PASS 559.69 seconds
TestRunner_l2cap-tester PASS 13.34 seconds
TestRunner_iso-tester PASS 9.70 seconds
TestRunner_bnep-tester PASS 2.91 seconds
TestRunner_mgmt-tester PASS 84.50 seconds
TestRunner_rfcomm-tester PASS 4.18 seconds
TestRunner_sco-tester PASS 5.20 seconds
TestRunner_ioctl-tester PASS 4.35 seconds
TestRunner_mesh-tester PASS 5.23 seconds
TestRunner_smp-tester PASS 4.05 seconds
TestRunner_userchan-tester PASS 3.02 seconds
TestRunner_6lowpan-tester PASS 4.19 seconds
IncrementalBuild PASS 43.26 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[v3,1/4] Bluetooth: hci_sync: Set random address on the set's handle
WARNING: Non-standard signature: Assisted-by:
#147:
Assisted-by: Claude:claude-opus-5.5
ERROR: Unrecognized email address: 'Claude:claude-opus-5.5'
#147:
Assisted-by: Claude:claude-opus-5.5
total: 1 errors, 1 warnings, 0 checks, 57 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/14973062.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/4] Bluetooth: hci_sync: Remove an advertising set by its handle
WARNING: Non-standard signature: Assisted-by:
#151:
Assisted-by: Claude:claude-opus-5.5
ERROR: Unrecognized email address: 'Claude:claude-opus-5.5'
#151:
Assisted-by: Claude:claude-opus-5.5
total: 1 errors, 1 warnings, 0 checks, 68 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/14973063.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,3/4] Bluetooth: hci_core: Add hci_free_adv_instance()
WARNING: Non-standard signature: Assisted-by:
#130:
Assisted-by: Claude:claude-opus-5.5
ERROR: Unrecognized email address: 'Claude:claude-opus-5.5'
#130:
Assisted-by: Claude:claude-opus-5.5
total: 1 errors, 1 warnings, 0 checks, 45 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/14973064.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,4/4] Bluetooth: hci_event: Find the owner of a terminated adv set
WARNING: Non-standard signature: Assisted-by:
#144:
Assisted-by: Claude:claude-opus-5.5
ERROR: Unrecognized email address: 'Claude:claude-opus-5.5'
#144:
Assisted-by: Claude:claude-opus-5.5
total: 1 errors, 1 warnings, 0 checks, 74 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/14973065.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: CheckSparse - WARNING
Desc: Run sparse tool with linux kernel
Output:
net/bluetooth/hci_event.c: note: in included file (through include/net/bluetooth/hci_core.h):
https://github.com/bluez/bluetooth-next/pull/1113
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-11-11 18:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 16:51 [PATCH v3 0/4] Bluetooth: Advertising sets on a single-set controller Weihong Guan
2026-11-11 16:51 ` [PATCH v3 1/4] Bluetooth: hci_sync: Set random address on the set's handle Weihong Guan
2026-11-11 18:21 ` bluez.test.bot [this message]
2026-11-11 16:51 ` [PATCH v3 2/4] Bluetooth: hci_sync: Remove an advertising set by its handle Weihong Guan
2026-11-11 16:51 ` [PATCH v3 3/4] Bluetooth: hci_core: Add hci_free_adv_instance() Weihong Guan
2026-11-11 16:51 ` [PATCH v3 4/4] Bluetooth: hci_event: Find the owner of a terminated adv set Weihong Guan
2026-11-11 20:20 ` [PATCH v3 0/4] Bluetooth: Advertising sets on a single-set controller patchwork-bot+bluetooth
-- strict thread matches above, loose matches on Subject: below --
2026-11-11 1:09 [PATCH v2 1/3] Bluetooth: hci_sync: Set an advertising set's random address on its handle Weihong Guan
2026-11-11 3:38 ` Bluetooth: Advertising sets on a single-set controller 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=6af4b224.b0b4b201.1d9e8.638a@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=weihong.guan@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