From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, hadess@hadess.net
Subject: RE: [BlueZ,v2,1/2] mpris-proxy: Fix possible crash
Date: Tue, 05 May 2026 05:29:45 -0700 (PDT) [thread overview]
Message-ID: <69f9e2b9.d40a0220.29f164.3055@mx.google.com> (raw)
In-Reply-To: <20260505104847.2550550-1-hadess@hadess.net>
[-- Attachment #1: Type: text/plain, Size: 826 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=1089833
---Test result---
Test Summary:
CheckPatch PASS 0.97 seconds
GitLint PASS 0.66 seconds
BuildEll PASS 19.94 seconds
BluezMake PASS 644.19 seconds
CheckSmatch PASS 347.95 seconds
bluezmakeextell PASS 180.52 seconds
IncrementalBuild PASS 652.82 seconds
ScanBuild PASS 1007.53 seconds
https://github.com/bluez/bluez/pull/2098
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-05-05 12:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 10:48 [BlueZ v2 1/2] mpris-proxy: Fix possible crash Bastien Nocera
2026-05-05 10:48 ` [BlueZ v2 2/2] mpris-proxy: Avoid session->obex dereference Bastien Nocera
2026-05-05 12:29 ` 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=69f9e2b9.d40a0220.29f164.3055@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