From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, zijun.hu@oss.qualcomm.com
Subject: RE: BlueZ: Add generic support for vendor HCI frames
Date: Mon, 20 Jul 2026 01:36:56 -0700 (PDT) [thread overview]
Message-ID: <6a5dde28.b5fdfa5d.50fed.a89b@mx.google.com> (raw)
In-Reply-To: <20260719-vendor_hci-v1-1-df2ac5a50117@oss.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 1624 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=1130548
---Test result---
Test Summary:
CheckPatch PASS 1.46 seconds
GitLint FAIL 1.02 seconds
BuildEll PASS 20.51 seconds
BluezMake PASS 548.95 seconds
MakeCheck PASS 18.66 seconds
MakeDistcheck PASS 159.62 seconds
CheckValgrind PASS 228.86 seconds
CheckSmatch WARNING 311.81 seconds
bluezmakeextell PASS 102.54 seconds
IncrementalBuild PASS 577.00 seconds
ScanBuild PASS 971.49 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[bluez,RFC,2/3] doc: hci-protocol: Add sock option BT_RCV_VENDOR_PKT for HCI_CHANNEL_USER
1: T1 Title exceeds max length (89>80): "[bluez,RFC,2/3] doc: hci-protocol: Add sock option BT_RCV_VENDOR_PKT for HCI_CHANNEL_USER"
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
monitor/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/2332
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-07-20 8:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 5:40 [PATCH bluez RFC 0/3] BlueZ: Add generic support for vendor HCI frames Zijun Hu
2026-07-20 5:40 ` [PATCH bluez RFC 1/3] doc: hci-protocol: Correct mtu to &mtu for getsockopt BT_RCVMTU Zijun Hu
2026-07-20 8:36 ` bluez.test.bot [this message]
2026-07-20 5:40 ` [PATCH bluez RFC 2/3] doc: hci-protocol: Add sock option BT_RCV_VENDOR_PKT for HCI_CHANNEL_USER Zijun Hu
2026-07-20 14:10 ` Luiz Augusto von Dentz
2026-07-21 9:07 ` Zijun Hu
2026-07-21 14:06 ` Luiz Augusto von Dentz
2026-07-21 20:42 ` Zijun Hu
2026-07-20 5:40 ` [PATCH bluez RFC 3/3] monitor: Add generic support for vendor HCI frames 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=6a5dde28.b5fdfa5d.50fed.a89b@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.