From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, naga.akella@oss.qualcomm.com
Subject: RE: RAP: streamline session handling, reflector setup
Date: Tue, 21 Jul 2026 02:48:39 -0700 (PDT) [thread overview]
Message-ID: <6a5f4077.b2d2c3b2.48f81.4265@mx.google.com> (raw)
In-Reply-To: <20260721084121.688467-2-naga.akella@oss.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 987 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=1131452
---Test result---
Test Summary:
CheckPatch PASS 0.89 seconds
GitLint PASS 0.50 seconds
BuildEll PASS 14.91 seconds
BluezMake PASS 369.85 seconds
MakeCheck PASS 0.83 seconds
MakeDistcheck PASS 118.70 seconds
CheckValgrind PASS 112.98 seconds
CheckSmatch PASS 203.48 seconds
bluezmakeextell PASS 73.27 seconds
IncrementalBuild PASS 371.90 seconds
ScanBuild PASS 626.25 seconds
https://github.com/bluez/bluez/pull/2336
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-07-21 9:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 8:41 [PATCH BlueZ v5 0/2] RAP: streamline session handling, reflector setup Naga Bhavani Akella
2026-07-21 8:41 ` [PATCH BlueZ v5 1/2] rap: use session lookup for RAS operations Naga Bhavani Akella
2026-07-21 9:48 ` bluez.test.bot [this message]
2026-07-21 8:41 ` [PATCH BlueZ v5 2/2] profiles: centralize reflector setup Naga Bhavani Akella
-- strict thread matches above, loose matches on Subject: below --
2026-07-27 6:59 [PATCH BlueZ v6 1/2] rap: use session lookup for RAS operations Naga Bhavani Akella
2026-07-27 8:52 ` RAP: streamline session handling, reflector setup bluez.test.bot
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=6a5f4077.b2d2c3b2.48f81.4265@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=naga.akella@oss.qualcomm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.