From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, cochcoder@proton.me
Subject: RE: [RFC] Bluetooth: btusb: use shared ACL buffers for TP-Link UB500
Date: Mon, 12 Oct 2026 21:24:02 -0700 (PDT) [thread overview]
Message-ID: <6acdb262.2eca3aba.37f0b8.105f@mx.google.com> (raw)
In-Reply-To: <20261013032742.497402-1-cochcoder@proton.me>
[-- Attachment #1: Type: text/plain, Size: 1815 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/1184337/
---Test result---
Test Summary:
CheckPatch PASS 0.96 seconds
VerifyFixes PASS 0.10 seconds
VerifySignedoff PASS 0.09 seconds
GitLint PASS 0.25 seconds
SubjectPrefix PASS 0.09 seconds
BuildKernel PASS 23.08 seconds
CheckAllWarning PASS 26.61 seconds
CheckSparse WARNING 28.16 seconds
BuildKernel32 PASS 23.23 seconds
CheckKernelLLVM PASS 26.84 seconds
TestRunnerSetup PASS 535.88 seconds
TestRunner_l2cap-tester PASS 13.73 seconds
TestRunner_iso-tester PASS 13.59 seconds
TestRunner_bnep-tester PASS 2.74 seconds
TestRunner_mgmt-tester PASS 83.63 seconds
TestRunner_rfcomm-tester PASS 12.45 seconds
TestRunner_sco-tester PASS 5.05 seconds
TestRunner_ioctl-tester PASS 4.23 seconds
TestRunner_mesh-tester PASS 5.07 seconds
TestRunner_smp-tester PASS 3.96 seconds
TestRunner_userchan-tester PASS 2.83 seconds
TestRunner_6lowpan-tester PASS 3.96 seconds
IncrementalBuild PASS 22.18 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):
https://github.com/bluez/bluetooth-next/pull/908
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-10-13 4:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 3:28 [RFC PATCH] Bluetooth: btusb: use shared ACL buffers for TP-Link UB500 Kyle Pepper
2026-10-13 4:24 ` 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=6acdb262.2eca3aba.37f0b8.105f@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=cochcoder@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