Linux bluetooth development
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, altomanigianluca@gmail.com
Subject: RE: Fix use-after-free in GATT client discovery
Date: Wed, 30 Sep 2026 08:13:34 -0700 (PDT)	[thread overview]
Message-ID: <6abd271e.a9f977cc.dd909.e3f9@mx.google.com> (raw)
In-Reply-To: <20260930093928.360745-2-altomanigianluca@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1021 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/1176731/

---Test result---

Test Summary:
CheckPatch                    PASS      1.06 seconds
GitLint                       PASS      0.69 seconds
BuildEll                      PASS      19.53 seconds
BluezMake                     PASS      392.19 seconds
MakeCheck                     PASS      1.11 seconds
MakeDistcheck                 PASS      139.36 seconds
CheckValgrind                 PASS      149.86 seconds
CheckSmatch                   PASS      289.11 seconds
bluezmakeextell               PASS      93.56 seconds
TestFunctional                PASS      1118.26 seconds
IncrementalBuild              PASS      394.02 seconds
ScanBuild                     PASS      1115.32 seconds



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

---
Regards,
Linux Bluetooth


  reply	other threads:[~2026-09-30 15:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-30  9:39 [PATCH BlueZ 0/2] Fix use-after-free in GATT client discovery Gianluca Altomani
2026-09-30  9:39 ` [PATCH BlueZ 1/2] shared/gatt-db: Always notify service removal Gianluca Altomani
2026-09-30 15:13   ` bluez.test.bot [this message]
2026-09-30  9:39 ` [PATCH BlueZ 2/2] shared/gatt-client: Fix double-queued service Gianluca Altomani

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=6abd271e.a9f977cc.dd909.e3f9@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=altomanigianluca@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /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