public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, iulia.tanasescu@nxp.com
Subject: RE: Split bt_iso_qos into dedicated structures
Date: Fri, 31 Mar 2023 10:10:30 -0700 (PDT)	[thread overview]
Message-ID: <64271406.370a0220.96076.3f09@mx.google.com> (raw)
In-Reply-To: <20230331153927.35411-2-iulia.tanasescu@nxp.com>

[-- Attachment #1: Type: text/plain, Size: 1185 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=735877

---Test result---

Test Summary:
CheckPatch                    PASS      0.87 seconds
GitLint                       PASS      0.33 seconds
BuildEll                      PASS      26.26 seconds
BluezMake                     PASS      761.90 seconds
MakeCheck                     PASS      10.89 seconds
MakeDistcheck                 PASS      150.00 seconds
CheckValgrind                 PASS      240.87 seconds
CheckSmatch                   WARNING   323.20 seconds
bluezmakeextell               PASS      97.50 seconds
IncrementalBuild              PASS      609.39 seconds
ScanBuild                     PASS      964.60 seconds

Details
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
emulator/bthost.c:584:28: warning: Variable length array is used.emulator/bthost.c:741:28: warning: Variable length array is used.


---
Regards,
Linux Bluetooth


  reply	other threads:[~2023-03-31 17:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-31 15:39 [PATCH BlueZ v3 0/1] Split bt_iso_qos into dedicated structures Iulia Tanasescu
2023-03-31 15:39 ` [PATCH BlueZ v3 1/1] " Iulia Tanasescu
2023-03-31 17:10   ` bluez.test.bot [this message]
2023-03-31 22:10 ` [PATCH BlueZ v3 0/1] " patchwork-bot+bluetooth
  -- strict thread matches above, loose matches on Subject: below --
2023-03-28  7:26 [PATCH BlueZ v2 1/1] " Iulia Tanasescu
2023-03-28  8:46 ` bluez.test.bot
2023-03-27 13:46 [PATCH BlueZ 1/1] " Iulia Tanasescu
2023-03-27 15:19 ` bluez.test.bot
2023-03-20 14:37 [PATCH BlueZ 1/8] btio: Use unicast structure for ISO QoS options Iulia Tanasescu
2023-03-20 15:11 ` Split bt_iso_qos into dedicated structures bluez.test.bot
2023-03-20 14:36 [PATCH 1/1] Bluetooth: " Iulia Tanasescu
2023-03-20 15:03 ` 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=64271406.370a0220.96076.3f09@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=iulia.tanasescu@nxp.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