From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: Bluetooth: Add support for HDT and EKS
Date: Fri, 06 Nov 2026 14:50:48 -0800 (PST) [thread overview]
Message-ID: <6aee59c8.714d0f95.45a9a.5649@mx.google.com> (raw)
In-Reply-To: <20261106181745.3134593-2-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2189 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/1204429/
---Test result---
Test Summary:
CheckPatch PASS 12.99 seconds
VerifyFixes PASS 0.13 seconds
VerifySignedoff PASS 0.13 seconds
GitLint PASS 1.93 seconds
SubjectPrefix PASS 0.74 seconds
BuildKernel PASS 23.90 seconds
CheckAllWarning PASS 27.96 seconds
CheckSparse WARNING 32.03 seconds
BuildKernel32 PASS 23.86 seconds
CheckKernelLLVM PASS 24.84 seconds
TestRunnerSetup PASS 553.02 seconds
TestRunner_l2cap-tester PASS 13.23 seconds
TestRunner_iso-tester PASS 9.68 seconds
TestRunner_bnep-tester PASS 2.99 seconds
TestRunner_mgmt-tester PASS 84.05 seconds
TestRunner_rfcomm-tester PASS 4.14 seconds
TestRunner_sco-tester PASS 5.19 seconds
TestRunner_ioctl-tester PASS 4.34 seconds
TestRunner_mesh-tester PASS 5.19 seconds
TestRunner_smp-tester PASS 4.06 seconds
TestRunner_userchan-tester PASS 2.96 seconds
TestRunner_6lowpan-tester PASS 12.60 seconds
IncrementalBuild PASS 106.40 seconds
Details
##############################
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):net/bluetooth/hci_event.c: note: in included file (through include/net/bluetooth/hci_core.h):net/bluetooth/hci_event.c: note: in included file (through include/net/bluetooth/hci_core.h):net/bluetooth/hci_event.c: note: in included file (through include/net/bluetooth/hci_core.h):net/bluetooth/hci_event.c: note: in included file (through include/net/bluetooth/hci_core.h):
https://github.com/bluez/bluetooth-next/pull/1081
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-11-06 22:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 18:17 [PATCH v8 0/6] Bluetooth: Add support for HDT and EKS Luiz Augusto von Dentz
2026-11-06 18:17 ` [PATCH v8 1/6] Bluetooth: Add initial support for HDT PHY Luiz Augusto von Dentz
2026-11-06 22:50 ` bluez.test.bot [this message]
2026-11-06 18:17 ` [PATCH v8 2/6] Bluetooth: ISO: Add extended QoS with the HDT rates Luiz Augusto von Dentz
2026-11-06 18:17 ` [PATCH v8 3/6] Bluetooth: Add initial support for EKS Luiz Augusto von Dentz
2026-11-06 18:17 ` [PATCH v8 4/6] Bluetooth: L2CAP: Add MIC length validation for HDT PHY Luiz Augusto von Dentz
2026-11-06 18:17 ` [PATCH v8 5/6] Bluetooth: Add HCI_OP_LE_SET_HDT_DEFAULT_PARAMS support Luiz Augusto von Dentz
2026-11-06 18:17 ` [PATCH v8 6/6] Bluetooth: Add EKS Opportunistic Encryption support Luiz Augusto von Dentz
-- strict thread matches above, loose matches on Subject: below --
2026-11-06 21:57 [PATCH v9 1/6] Bluetooth: Add initial support for HDT PHY Luiz Augusto von Dentz
2026-11-06 22:50 ` Bluetooth: Add support for HDT and EKS bluez.test.bot
2026-11-06 16:12 [PATCH v7 1/6] Bluetooth: Add initial support for HDT PHY Luiz Augusto von Dentz
2026-11-06 17:44 ` Bluetooth: Add support for HDT and EKS bluez.test.bot
2026-11-05 20:50 [PATCH v6 1/6] Bluetooth: Add initial support for HDT PHY Luiz Augusto von Dentz
2026-11-05 23:19 ` Bluetooth: Add support for HDT and EKS bluez.test.bot
2026-11-04 22:13 [PATCH v3 1/6] Bluetooth: Add initial support for HDT PHY Luiz Augusto von Dentz
2026-11-05 2:35 ` Bluetooth: Add support for HDT and EKS bluez.test.bot
2026-11-04 18:36 [PATCH v2 1/6] Bluetooth: Add initial support for HDT PHY Luiz Augusto von Dentz
2026-11-04 22:25 ` Bluetooth: Add support for HDT and EKS 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=6aee59c8.714d0f95.45a9a.5649@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@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 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.