From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, hadess@hadess.net
Subject: RE: [RFC,BlueZ] media: Fix possible crash on exit/adapter removal
Date: Tue, 12 May 2026 05:26:55 -0700 (PDT) [thread overview]
Message-ID: <6a031c8f.050a0220.1cf1f9.b06e@mx.google.com> (raw)
In-Reply-To: <20260512101431.2017966-1-hadess@hadess.net>
[-- Attachment #1: Type: text/plain, Size: 989 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=1093445
---Test result---
Test Summary:
CheckPatch PASS 0.43 seconds
GitLint PASS 0.29 seconds
BuildEll PASS 20.29 seconds
BluezMake PASS 657.53 seconds
MakeCheck PASS 2.98 seconds
MakeDistcheck PASS 246.45 seconds
CheckValgrind PASS 226.08 seconds
CheckSmatch PASS 350.07 seconds
bluezmakeextell PASS 181.48 seconds
IncrementalBuild PASS 664.24 seconds
ScanBuild PASS 1027.26 seconds
https://github.com/bluez/bluez/pull/2122
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-05-12 12:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 10:14 [RFC BlueZ] media: Fix possible crash on exit/adapter removal Bastien Nocera
2026-05-12 12:26 ` 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=6a031c8f.050a0220.1cf1f9.b06e@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=hadess@hadess.net \
--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