From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, NoahWeinberger2003@proton.me
Subject: RE: Bluetooth: validate retained LE Set Ext Adv Enable command length
Date: Sun, 08 Nov 2026 15:47:08 -0800 (PST) [thread overview]
Message-ID: <6af109fc.31957b85.1984ae.4ea9@mx.google.com> (raw)
In-Reply-To: <DiB5DgYqITLLCcetFLdSxmGUcDfzozcvmS5i8Owo6GfN9hpcRbpu3W2uQPmg_oSz52yjRq9uh49bQtOFPli5RZf0_IrM_S4cqdRQhax-m8g=@proton.me>
[-- Attachment #1: Type: text/plain, Size: 3667 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/1205518/
---Test result---
Test Summary:
CheckPatch FAIL 2.91 seconds
VerifyFixes PASS 0.11 seconds
VerifySignedoff PASS 0.11 seconds
GitLint FAIL 0.30 seconds
SubjectPrefix PASS 0.11 seconds
BuildKernel PASS 30.86 seconds
CheckAllWarning PASS 35.34 seconds
CheckSparse WARNING 37.92 seconds
BuildKernel32 PASS 30.57 seconds
CheckKernelLLVM PASS 34.85 seconds
TestRunnerSetup PASS 743.90 seconds
TestRunner_l2cap-tester PASS 12.91 seconds
TestRunner_iso-tester PASS 11.02 seconds
TestRunner_bnep-tester PASS 3.16 seconds
TestRunner_mgmt-tester PASS 88.84 seconds
TestRunner_rfcomm-tester PASS 14.90 seconds
TestRunner_sco-tester PASS 5.72 seconds
TestRunner_ioctl-tester PASS 4.72 seconds
TestRunner_mesh-tester PASS 5.60 seconds
TestRunner_smp-tester PASS 4.39 seconds
TestRunner_userchan-tester PASS 3.24 seconds
TestRunner_6lowpan-tester PASS 4.48 seconds
IncrementalBuild PASS 29.25 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
Bluetooth: validate retained LE Set Ext Adv Enable command length
WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#103:
Affected version/commit: mainline fa4ad798f6f681031775266044ba1b0cf3c670bd (v7.4-rc1, 2026-11-07), net/bluetooth/hci_event.c:1669-1735 (hci_cc_le_set_ext_adv_enable).
WARNING: Reported-by: should be immediately followed by Closes: or Link: with a URL to the report
#113:
Reported-by: Noah Weinberger <noahweinberger2003@proton.me>
ERROR: Missing Signed-off-by: line(s)
total: 1 errors, 2 warnings, 0 checks, 19 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/14962585.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:
Bluetooth: validate retained LE Set Ext Adv Enable command length
1: CC1 Body does not contain a 'Signed-off-by' line
23: B1 Line exceeds max length (166>80): "Affected version/commit: mainline fa4ad798f6f681031775266044ba1b0cf3c670bd (v7.4-rc1, 2026-11-07), net/bluetooth/hci_event.c:1669-1735 (hci_cc_le_set_ext_adv_enable)."
24: B1 Line exceeds max length (122>80): "Handler is longstanding; the fix class was established this window by ed4d302af7 (CIG params) and 1eb52f35fc (Create CIS)."
27: B1 Line exceeds max length (124>80): "mainline fa4ad798f6f681031775266044ba1b0cf3c670bd (v7.4-rc1, 2026-11-07); every code path cited below was re-verified by the"
##############################
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/1090
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-11-08 23:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-08 22:28 [PATCH] Bluetooth: validate retained LE Set Ext Adv Enable command length Noah Weinberger
2026-11-08 23:47 ` bluez.test.bot [this message]
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=6af109fc.31957b85.1984ae.4ea9@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=NoahWeinberger2003@proton.me \
--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