Linux bluetooth development
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, naga.akella@oss.qualcomm.com
Subject: RE: doc: Add CS distance provider documentation
Date: Fri, 31 Jul 2026 01:00:02 -0700 (PDT)	[thread overview]
Message-ID: <6a6c5602.6c5720b3.159f43.a64c@mx.google.com> (raw)
In-Reply-To: <20260731070159.2769120-2-naga.akella@oss.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=1137931

---Test result---

Test Summary:
CheckPatch                    PASS      0.87 seconds
GitLint                       PASS      0.64 seconds
BuildEll                      PASS      15.40 seconds
BluezMake                     PASS      398.30 seconds
MakeCheck                     PASS      17.66 seconds
MakeDistcheck                 PASS      127.87 seconds
CheckValgrind                 PASS      181.44 seconds
CheckSmatch                   PASS      211.07 seconds
bluezmakeextell               PASS      76.64 seconds
IncrementalBuild              PASS      428.77 seconds
ScanBuild                     PASS      680.83 seconds



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

---
Regards,
Linux Bluetooth


  reply	other threads:[~2026-07-31  8:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-31  7:01 [PATCH BlueZ v2 0/3] doc: Add CS distance provider documentation Naga Bhavani Akella
2026-07-31  7:01 ` [PATCH BlueZ v2 1/3] doc: Add org.bluez.CSDistance1 documentation Naga Bhavani Akella
2026-07-31  8:00   ` bluez.test.bot [this message]
2026-07-31  7:01 ` [PATCH BlueZ v2 2/3] doc: Add org.bluez.CSDistanceProvider documentation Naga Bhavani Akella
2026-07-31  7:01 ` [PATCH BlueZ v2 3/3] doc: Add org.bluez.CSDistanceProviderManager documentation Naga Bhavani Akella

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=6a6c5602.6c5720b3.159f43.a64c@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox