Linux bluetooth development
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, prathibha.madugonde@oss.qualcomm.com
Subject: RE: [BlueZ] shared/rap: Add client ranging registration and notification parsing
Date: Thu, 04 Jun 2026 05:06:58 -0700 (PDT)	[thread overview]
Message-ID: <6a216a62.d68db960.2a81fb.6947@mx.google.com> (raw)
In-Reply-To: <20260604085205.4135084-1-prathm@qti.qualcomm.com>

[-- Attachment #1: Type: text/plain, Size: 988 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=1105806

---Test result---

Test Summary:
CheckPatch                    PASS      0.67 seconds
GitLint                       PASS      0.19 seconds
BuildEll                      PASS      16.38 seconds
BluezMake                     PASS      497.78 seconds
MakeCheck                     PASS      0.76 seconds
MakeDistcheck                 PASS      184.57 seconds
CheckValgrind                 PASS      157.05 seconds
CheckSmatch                   PASS      250.35 seconds
bluezmakeextell               PASS      128.31 seconds
IncrementalBuild              PASS      502.61 seconds
ScanBuild                     PASS      727.00 seconds



https://github.com/bluez/bluez/pull/2175

---
Regards,
Linux Bluetooth


  reply	other threads:[~2026-06-04 12:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-04  8:52 [PATCH BlueZ] shared/rap: Add client ranging registration and notification parsing Prathibha Madugonde
2026-06-04 12:06 ` bluez.test.bot [this message]
2026-06-04 19:40 ` patchwork-bot+bluetooth

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=6a216a62.d68db960.2a81fb.6947@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=prathibha.madugonde@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox