From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, qwe.aldo@gmail.com
Subject: RE: [v4] Bluetooth: SCO: serialise sco_conn lifetime against sco_recv_scodata()
Date: Sun, 27 Sep 2026 16:22:56 -0700 (PDT) [thread overview]
Message-ID: <6ab9a550.edd3b74b.2ac4ed.0ec0@mx.google.com> (raw)
In-Reply-To: <20260926212145.1343318-1-qwe.aldo@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1312 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/1174573/
---Test result---
Test Summary:
CheckPatch PASS 2.43 seconds
VerifyFixes PASS 0.09 seconds
VerifySignedoff PASS 0.11 seconds
GitLint PASS 0.53 seconds
SubjectPrefix PASS 0.09 seconds
BuildKernel PASS 27.99 seconds
CheckAllWarning PASS 31.66 seconds
CheckSparse WARNING 34.44 seconds
BuildKernel32 PASS 27.44 seconds
CheckKernelLLVM PASS 31.03 seconds
TestRunnerSetup PASS 701.58 seconds
TestRunner_sco-tester PASS 8.45 seconds
IncrementalBuild PASS 25.66 seconds
Details
##############################
Test: CheckSparse - WARNING
Desc: Run sparse tool with linux kernel
Output:
net/bluetooth/sco.c: note: in included file:./include/net/bluetooth/hci_core.h:151:35: warning: array of flexible structures
https://github.com/bluez/bluetooth-next/pull/827
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-09-27 23:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 12:20 [PATCH v3] Bluetooth: SCO: serialise sco_conn lifetime against sco_recv_scodata() Aldo Ariel Panzardo
2026-09-23 15:54 ` [v3] " bluez.test.bot
2026-09-26 21:21 ` [PATCH v4] " Aldo Ariel Panzardo
2026-09-27 23:22 ` bluez.test.bot [this message]
2026-09-28 17:30 ` patchwork-bot+bluetooth
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=6ab9a550.edd3b74b.2ac4ed.0ec0@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=qwe.aldo@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.