Linux bluetooth development
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, frederic.danis@collabora.com
Subject: RE: mgmt/device: report link security level to D-Bus clients
Date: Fri, 25 Sep 2026 08:41:00 -0700 (PDT)	[thread overview]
Message-ID: <6ab6960c.17b2f02a.51de4.9415@mx.google.com> (raw)
In-Reply-To: <20260925102914.3282319-2-frederic.danis@collabora.com>

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

---Test result---

Test Summary:
CheckPatch                    PASS      2.27 seconds
GitLint                       PASS      1.48 seconds
BuildEll                      PASS      16.45 seconds
BluezMake                     PASS      278.23 seconds
MakeCheck                     PASS      14.50 seconds
MakeDistcheck                 PASS      116.51 seconds
CheckValgrind                 PASS      182.99 seconds
CheckSmatch                   WARNING   217.58 seconds
bluezmakeextell               PASS      71.93 seconds
TestFunctional                PASS      895.09 seconds
IncrementalBuild              PASS      351.02 seconds
ScanBuild                     PASS      809.74 seconds

Details
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
monitor/packet.c:2289:26: warning: Variable length array is used.monitor/packet.c: note: in included file:monitor/bt.h:3924:52: warning: array of flexible structuresmonitor/bt.h:3912:40: warning: array of flexible structures


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

---
Regards,
Linux Bluetooth


  reply	other threads:[~2026-09-25 15:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-25 10:29 [PATCH BlueZ v3 RESEND 0/6] mgmt/device: report link security level to D-Bus clients Frédéric Danis
2026-09-25 10:29 ` [PATCH BlueZ v3 RESEND 1/6] mgmt: Add Security Level Changed event Frédéric Danis
2026-09-25 15:41   ` bluez.test.bot [this message]
2026-09-25 10:29 ` [PATCH BlueZ v3 RESEND 2/6] mgmt-tester: Add Security Level Changed event tests Frédéric Danis
2026-09-25 10:29 ` [PATCH BlueZ v3 RESEND 3/6] monitor: Add support for Mgmt Security Level changed event Frédéric Danis
2026-09-25 10:29 ` [PATCH BlueZ v3 RESEND 4/6] device: Add SecurityLevel properties to org.bluez.Device1 Frédéric Danis
2026-09-25 10:29 ` [PATCH BlueZ v3 RESEND 5/6] org.bluez.Device: Add Security Level related properties Frédéric Danis
2026-09-25 10:29 ` [PATCH BlueZ v3 RESEND 6/6] client: Display SecurityLevel in device info Frédéric Danis
  -- strict thread matches above, loose matches on Subject: below --
2026-09-29 10:19 [PATCH BlueZ v4 1/6] mgmt: Add Security Level Changed event Frédéric Danis
2026-09-29 14:42 ` mgmt/device: report link security level to D-Bus clients bluez.test.bot
2026-08-21  9:09 [PATCH BlueZ v3 1/6] mgmt: Add Security Level Changed event Frédéric Danis
2026-08-21 10:20 ` mgmt/device: report link security level to D-Bus clients bluez.test.bot
2026-09-10 18:22 ` bluez.test.bot
2026-08-20 12:58 [PATCH BlueZ v2 1/6] mgmt: Add Security Level Changed event Frédéric Danis
2026-08-20 14:07 ` mgmt/device: report link security level to D-Bus clients bluez.test.bot
2026-08-20 10:52 [PATCH BlueZ 1/6] mgmt: Add Security Level Changed event Frédéric Danis
2026-08-20 11:08 ` mgmt/device: report link security level to D-Bus clients bluez.test.bot

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=6ab6960c.17b2f02a.51de4.9415@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=frederic.danis@collabora.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