From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, pav@iki.fi
Subject: RE: Bluetooth: enable context analysis
Date: Sat, 16 May 2026 05:46:31 -0700 (PDT) [thread overview]
Message-ID: <6a086727.f3350d4a.330d6d.8493@mx.google.com> (raw)
In-Reply-To: <342a530a1756cfd136542a33e5d947fd6c0a85d2.1778930064.git.pav@iki.fi>
[-- Attachment #1: Type: text/plain, Size: 2120 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=1095802
---Test result---
Test Summary:
CheckPatch PASS 3.56 seconds
GitLint FAIL 1.79 seconds
SubjectPrefix PASS 0.59 seconds
BuildKernel PASS 26.34 seconds
CheckAllWarning PASS 29.76 seconds
CheckSparse PASS 30.21 seconds
BuildKernel32 PASS 28.37 seconds
TestRunnerSetup PASS 552.61 seconds
TestRunner_l2cap-tester PASS 379.41 seconds
TestRunner_iso-tester PASS 591.09 seconds
TestRunner_bnep-tester PASS 18.71 seconds
TestRunner_mgmt-tester PASS 2023.25 seconds
TestRunner_rfcomm-tester PASS 63.64 seconds
TestRunner_sco-tester PASS 141.94 seconds
TestRunner_ioctl-tester PASS 133.61 seconds
TestRunner_mesh-tester PASS 60.34 seconds
TestRunner_smp-tester PASS 18.18 seconds
TestRunner_userchan-tester PASS 19.47 seconds
TestRunner_6lowpan-tester PASS 51.14 seconds
IncrementalBuild PASS 32.11 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[RFC,3/5] Bluetooth: ISO: lock same hdev as what is released
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
11: B1 Line exceeds max length (87>80): "net/bluetooth/iso.c:1095:2: warning: releasing mutex 'iso_conn_get_hdev(sk->conn).lock'"
https://github.com/bluez/bluetooth-next/pull/202
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-05-16 12:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-16 11:14 [RFC PATCH 0/5] Bluetooth: enable context analysis Pauli Virtanen
2026-05-16 11:14 ` [RFC PATCH 1/5] Bluetooth: af_bluetooth: Add minimal context analysis annotations Pauli Virtanen
2026-05-16 12:46 ` bluez.test.bot [this message]
2026-05-16 11:14 ` [RFC PATCH 2/5] Bluetooth: hci_core: " Pauli Virtanen
2026-05-16 11:14 ` [RFC PATCH 3/5] Bluetooth: ISO: lock same hdev as what is released Pauli Virtanen
2026-05-16 11:14 ` [RFC PATCH 4/5] Bluetooth: L2CAP: Add minimal context analysis annotations Pauli Virtanen
2026-05-16 11:14 ` [RFC PATCH 5/5] Bluetooth: enable context analysis Pauli Virtanen
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=6a086727.f3350d4a.330d6d.8493@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pav@iki.fi \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.