From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, rollkingzzc@gmail.com
Subject: RE: [v2] Bluetooth: 6lowpan: Fix peer and channel lifetime during teardown
Date: Sat, 09 May 2026 21:38:14 -0700 (PDT) [thread overview]
Message-ID: <6a000bb6.050a0220.6094.0ded@mx.google.com> (raw)
In-Reply-To: <20260510040424.2054614-1-rollkingzzc@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2393 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=1092168
---Test result---
Test Summary:
CheckPatch FAIL 0.81 seconds
GitLint FAIL 0.33 seconds
SubjectPrefix PASS 0.13 seconds
BuildKernel PASS 27.24 seconds
CheckAllWarning PASS 29.84 seconds
CheckSparse PASS 28.98 seconds
BuildKernel32 PASS 26.59 seconds
TestRunnerSetup PASS 571.72 seconds
TestRunner_6lowpan-tester PASS 58.20 seconds
IncrementalBuild PASS 28.09 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[v2] Bluetooth: 6lowpan: Fix peer and channel lifetime during teardown
WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#126:
The buggy scenario involves two paths, with each column showing the order within that path:
total: 0 errors, 1 warnings, 0 checks, 239 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/14563451.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:
[v2] Bluetooth: 6lowpan: Fix peer and channel lifetime during teardown
WARNING: I3 - ignore-body-lines: gitlint will be switching from using Python regex 'match' (match beginning) to 'search' (match anywhere) semantics. Please review your ignore-body-lines.regex option accordingly. To remove this warning, set general.regex-style-search=True. More details: https://jorisroovers.github.io/gitlint/configuration/#regex-style-search
24: B1 Line exceeds max length (91>80): "The buggy scenario involves two paths, with each column showing the order within that path:"
https://github.com/bluez/bluetooth-next/pull/162
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-05-10 4:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-09 17:37 [PATCH] Bluetooth: 6lowpan: Defer peer channel release until RCU cleanup Zhang Cen
2026-05-09 18:29 ` bluez.test.bot
2026-05-10 1:43 ` [PATCH] " Hillf Danton
2026-05-10 4:01 ` c Z
2026-05-10 4:04 ` [PATCH v2] Bluetooth: 6lowpan: Fix peer and channel lifetime during teardown Zhang Cen
2026-05-10 4:38 ` bluez.test.bot [this message]
2026-05-11 16:20 ` Luiz Augusto von Dentz
2026-05-11 17:11 ` Cen Zhang
2026-05-11 17:18 ` [PATCH v3] " Zhang Cen
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=6a000bb6.050a0220.6094.0ded@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=rollkingzzc@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