From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, ooonea@gmail.com
Subject: RE: [BlueZ,v2,1/2] input: Reset report map state on detach
Date: Fri, 25 Sep 2026 18:30:38 -0700 (PDT) [thread overview]
Message-ID: <6ab7203e.ec46f90a.25b39.52f6@mx.google.com> (raw)
In-Reply-To: <CACmoRBZ-pHuzAUrGK39O_1s1xkbvH5GubRnqtuOELU-Cv8Q6uQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1019 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/1174115/
---Test result---
Test Summary:
CheckPatch PASS 0.37 seconds
GitLint PASS 0.26 seconds
BuildEll PASS 17.11 seconds
BluezMake PASS 303.54 seconds
MakeCheck PASS 0.85 seconds
MakeDistcheck PASS 127.51 seconds
CheckValgrind PASS 131.50 seconds
CheckSmatch PASS 222.20 seconds
bluezmakeextell PASS 83.48 seconds
TestFunctional PASS 964.15 seconds
IncrementalBuild PASS 305.70 seconds
ScanBuild PASS 881.88 seconds
https://github.com/bluez/bluez/pull/2592
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-09-26 1:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 17:42 [PATCH BlueZ 1/2] input: Reset report map state on detach Giuseppe Piscitelli
2026-09-25 17:43 ` [PATCH BlueZ 2/2] unit: Test HoG report map reads after reconnect Giuseppe Piscitelli
2026-09-25 20:05 ` [BlueZ,1/2] input: Reset report map state on detach bluez.test.bot
2026-09-25 22:03 ` [PATCH BlueZ v2 1/2] " Giuseppe Piscitelli
2026-09-26 1:30 ` bluez.test.bot [this message]
2026-09-25 22:03 ` [PATCH BlueZ v2 2/2] unit: Test HoG report map reads after reconnect Giuseppe Piscitelli
2026-09-28 17:48 ` [PATCH BlueZ 1/2] input: Reset report map state on detach Luiz Augusto von Dentz
2026-09-28 21:03 ` Giuseppe Piscitelli
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=6ab7203e.ec46f90a.25b39.52f6@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=ooonea@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox