From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, derektern@proton.me
Subject: RE: BAP transport Release and reacquire fixes
Date: Tue, 06 Oct 2026 09:43:26 -0700 (PDT) [thread overview]
Message-ID: <6ac5252e.e782ec0c.364fd1.6eb5@mx.google.com> (raw)
In-Reply-To: <PYDC9kPUFiayBviaLIJziLbacU4BWxj1nr2x3XTYoyuEajR8F_65ogs4D3OS3dMS7pzzn-x-4ekzVz2lfDRlyviCh5T-ZRm6GV-wtf-Ud0s=@proton.me>
[-- Attachment #1: Type: text/plain, Size: 1022 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/1180235/
---Test result---
Test Summary:
CheckPatch PASS 1.23 seconds
GitLint PASS 1.21 seconds
BuildEll PASS 19.40 seconds
BluezMake PASS 392.20 seconds
MakeCheck PASS 14.09 seconds
MakeDistcheck PASS 138.44 seconds
CheckValgrind PASS 229.50 seconds
CheckSmatch PASS 287.01 seconds
bluezmakeextell PASS 92.95 seconds
TestFunctional PASS 1139.30 seconds
IncrementalBuild PASS 397.83 seconds
ScanBuild PASS 1103.29 seconds
https://github.com/bluez/bluez/pull/2629
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-10-06 16:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 10:59 [PATCH BlueZ v2 0/3] BAP transport Release and reacquire fixes dt
2026-10-06 11:00 ` [PATCH BlueZ v2 1/3] transport: Preserve Release on late BAP ready dt
2026-10-06 16:43 ` bluez.test.bot [this message]
2026-10-06 11:00 ` [PATCH BlueZ v2 2/3] bap: Recreate stream IO after an early Enable dt
2026-10-06 11:01 ` [PATCH BlueZ v2 3/3] test: Cover BAP transport release and reacquire dt
2026-10-07 18:40 ` [PATCH BlueZ v2 0/3] BAP transport Release and reacquire fixes 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=6ac5252e.e782ec0c.364fd1.6eb5@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=derektern@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