Linux bluetooth development
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,v1,1/2] ranging: Issue CS Security Enable based on the ACL role
Date: Tue, 27 Oct 2026 08:20:21 -0700 (PDT)	[thread overview]
Message-ID: <6ae0c135.399bf8e8.2794b0.1f48@mx.google.com> (raw)
In-Reply-To: <20261027140953.1854740-1-luiz.dentz@gmail.com>

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

---Test result---

Test Summary:
CheckPatch                    PASS      1.11 seconds
GitLint                       PASS      0.69 seconds
BuildEll                      PASS      19.68 seconds
BluezMake                     PASS      304.29 seconds
CheckSmatch                   PASS      297.45 seconds
bluezmakeextell               PASS      95.34 seconds
TestFunctional                PASS      1130.04 seconds
IncrementalBuild              PASS      302.83 seconds
ScanBuild                     PASS      1160.14 seconds



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

---
Regards,
Linux Bluetooth


  parent reply	other threads:[~2026-10-27 15:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-27 14:09 [PATCH BlueZ v1 1/2] ranging: Issue CS Security Enable based on the ACL role Luiz Augusto von Dentz
2026-10-27 14:09 ` [PATCH BlueZ v1 2/2] ranging: Fail CS Config Complete on role mismatch Luiz Augusto von Dentz
2026-10-27 15:20 ` bluez.test.bot [this message]
2026-10-28 13:30 ` [PATCH BlueZ v1 1/2] ranging: Issue CS Security Enable based on the ACL role 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=6ae0c135.399bf8e8.2794b0.1f48@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.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