All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, proxy-alt@proxy-alt.dev
Subject: RE: [v2] shared/gatt-client: discover the CCC descriptor instead of assuming it
Date: Fri, 07 Aug 2026 23:10:26 -0700 (PDT)	[thread overview]
Message-ID: <6a76c852.881e6cae.4accd.b68b@mx.google.com> (raw)
In-Reply-To: <20260808044531.71229-1-proxy-alt@proxy-alt.dev>

[-- 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=1142530

---Test result---

Test Summary:
CheckPatch                    PASS      0.41 seconds
GitLint                       PASS      0.25 seconds
BuildEll                      PASS      20.17 seconds
BluezMake                     PASS      532.41 seconds
MakeCheck                     PASS      19.72 seconds
MakeDistcheck                 PASS      152.93 seconds
CheckValgrind                 PASS      222.95 seconds
CheckSmatch                   PASS      294.26 seconds
bluezmakeextell               PASS      95.51 seconds
IncrementalBuild              PASS      532.08 seconds
ScanBuild                     PASS      864.11 seconds



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

---
Regards,
Linux Bluetooth


      reply	other threads:[~2026-08-08  6:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-08  3:19 [PATCH BlueZ] shared/gatt-client: discover the CCC descriptor instead of assuming it Proxy alt
2026-08-08  4:16 ` Proxy alt
2026-08-08  4:34 ` [BlueZ] " bluez.test.bot
2026-08-08  4:45 ` [PATCH v2] " Proxy alt
2026-08-08  6:10   ` 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=6a76c852.881e6cae.4accd.b68b@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=proxy-alt@proxy-alt.dev \
    /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.