All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: Add tests for security of deferred setup
Date: Fri, 20 Nov 2026 14:28:57 -0800 (PST)	[thread overview]
Message-ID: <6b00c9a9.7724c133.1c6204.87c1@mx.google.com> (raw)
In-Reply-To: <20261120154750.1745643-2-luiz.dentz@gmail.com>

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

---Test result---

Test Summary:
CheckPatch                    PASS      2.20 seconds
GitLint                       PASS      1.33 seconds
BuildEll                      PASS      15.89 seconds
BluezMake                     PASS      229.33 seconds
CheckSmatch                   WARNING   235.46 seconds
bluezmakeextell               PASS      75.15 seconds
TestFunctional                PASS      1003.87 seconds
IncrementalBuild              PASS      259.99 seconds
ScanBuild                     PASS      839.30 seconds

Details
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
emulator/bthost.c:713:28: warning: Variable length array is used.emulator/bthost.c:714:32: warning: Variable length array is used.emulator/bthost.c:967:28: warning: Variable length array is used.emulator/bthost.c:1001:28: warning: Variable length array is used.emulator/bthost.c:1002:32: warning: Variable length array is used.


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

---
Regards,
Linux Bluetooth


  reply	other threads:[~2026-11-20 22:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-20 15:47 [PATCH BlueZ v2 0/5] Add tests for security of deferred setup Luiz Augusto von Dentz
2026-11-20 15:47 ` [PATCH BlueZ v2 1/5] emulator/bthost: Add helpers to test " Luiz Augusto von Dentz
2026-11-20 22:28   ` bluez.test.bot [this message]
2026-11-20 15:47 ` [PATCH BlueZ v2 2/5] emulator/btdev: Add btdev_set_link_key_type Luiz Augusto von Dentz
2026-11-20 15:47 ` [PATCH BlueZ v2 3/5] l2cap-tester: Add tests for security of deferred setup Luiz Augusto von Dentz
2026-11-20 15:47 ` [PATCH BlueZ v2 4/5] rfcomm-tester: Add tests for " Luiz Augusto von Dentz
2026-11-20 15:47 ` [PATCH BlueZ v2 5/5] l2cap-tester: Set IO capability in Client SSP - Success 2 Luiz Augusto von Dentz
  -- strict thread matches above, loose matches on Subject: below --
2026-11-19 22:15 [PATCH BlueZ v1 1/3] emulator/bthost: Add helpers to test security of deferred setup Luiz Augusto von Dentz
2026-11-20  0:55 ` Add tests for " 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=6b00c9a9.7724c133.1c6204.87c1@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 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.