From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, frederic.danis@collabora.com
Subject: RE: [BlueZ,v2] audio/avrcp: Poll GetPlayStatus when position changed event unsupported
Date: Fri, 25 Sep 2026 08:58:20 -0700 (PDT) [thread overview]
Message-ID: <6ab69a1c.81b1ab59.de404.c888@mx.google.com> (raw)
In-Reply-To: <20260925141047.3397212-1-frederic.danis@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 1316 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/1173825/
---Test result---
Test Summary:
CheckPatch PASS 0.39 seconds
GitLint FAIL 0.22 seconds
BuildEll PASS 19.56 seconds
BluezMake PASS 381.03 seconds
MakeCheck PASS 2.72 seconds
MakeDistcheck PASS 140.31 seconds
CheckValgrind PASS 150.60 seconds
CheckSmatch PASS 290.33 seconds
bluezmakeextell PASS 95.40 seconds
TestFunctional PASS 1109.57 seconds
IncrementalBuild PASS 375.13 seconds
ScanBuild PASS 1132.95 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[BlueZ,v2] audio/avrcp: Poll GetPlayStatus when position changed event unsupported
1: T1 Title exceeds max length (82>80): "[BlueZ,v2] audio/avrcp: Poll GetPlayStatus when position changed event unsupported"
https://github.com/bluez/bluez/pull/2589
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-09-25 15:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 14:10 [PATCH BlueZ v2] audio/avrcp: Poll GetPlayStatus when position changed event unsupported Frédéric Danis
2026-09-25 15:58 ` 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=6ab69a1c.81b1ab59.de404.c888@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=frederic.danis@collabora.com \
--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