All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, zijun.hu@oss.qualcomm.com
Subject: RE: BlueZ: Support vendor packets
Date: Thu, 03 Sep 2026 08:53:33 -0700 (PDT)	[thread overview]
Message-ID: <6a9997fd.6da061a6.2816fc.db92@mx.google.com> (raw)
In-Reply-To: <20260903-vendor_hci-v3-1-015d62a57c91@oss.qualcomm.com>

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

---Test result---

Test Summary:
CheckPatch                    PASS      1.27 seconds
GitLint                       FAIL      0.86 seconds
BuildEll                      PASS      20.46 seconds
BluezMake                     PASS      607.30 seconds
MakeCheck                     PASS      19.51 seconds
MakeDistcheck                 PASS      163.48 seconds
CheckValgrind                 PASS      235.45 seconds
CheckSmatch                   WARNING   317.06 seconds
bluezmakeextell               PASS      104.20 seconds
IncrementalBuild              PASS      663.91 seconds
ScanBuild                     PASS      1011.07 seconds

Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[BlueZ,v3,1/4] doc/hci-protocol: Fix missing & on mtu argument in BT_RCVMTU example

1: T1 Title exceeds max length (83>80): "[BlueZ,v3,1/4] doc/hci-protocol: Fix missing & on mtu argument in BT_RCVMTU example"
[BlueZ,v3,3/4] doc/hci-protocol: Add BT_RECV_VENDOR_PKT socket option for HCI_CHANNEL_USER

1: T1 Title exceeds max length (90>80): "[BlueZ,v3,3/4] doc/hci-protocol: Add BT_RECV_VENDOR_PKT socket option for HCI_CHANNEL_USER"
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
monitor/msft.c: note: in included file:monitor/msft.h:88:44: warning: array of flexible structuresmonitor/packet.c:2003: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 structuresmonitor/packet.c:2003: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/2481

---
Regards,
Linux Bluetooth


  reply	other threads:[~2026-09-03 15:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-03 14:47 [PATCH BlueZ v3 0/4] BlueZ: Support vendor packets Zijun Hu
2026-09-03 14:47 ` [PATCH BlueZ v3 1/4] doc/hci-protocol: Fix missing & on mtu argument in BT_RCVMTU example Zijun Hu
2026-09-03 15:53   ` bluez.test.bot [this message]
2026-09-03 14:47 ` [PATCH BlueZ v3 2/4] monitor: s/vendor_(evt|event)/\1_vendor/ Zijun Hu
2026-09-03 14:47 ` [PATCH BlueZ v3 3/4] doc/hci-protocol: Add BT_RECV_VENDOR_PKT socket option for HCI_CHANNEL_USER Zijun Hu
2026-09-03 15:16   ` Luiz Augusto von Dentz
2026-09-04 14:12     ` Zijun Hu
2026-09-04 14:31       ` Luiz Augusto von Dentz
2026-09-06  2:27         ` Zijun Hu
2026-09-03 14:47 ` [PATCH BlueZ v3 4/4] monitor: Support vendor packets Zijun Hu

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=6a9997fd.6da061a6.2816fc.db92@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=zijun.hu@oss.qualcomm.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.