From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, wolozgabriel@gmail.com
Subject: RE: lib/bluetooth/mgmt: Add missing mgmt_op entry for HCI_CMD_SYNC
Date: Sun, 08 Mar 2026 23:21:40 -0700 (PDT) [thread overview]
Message-ID: <69ae66f4.050a0220.22b4c6.50f5@mx.google.com> (raw)
In-Reply-To: <20260309045902.2354-2-wolozgabriel@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1261 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=1063415
---Test result---
Test Summary:
CheckPatch PENDING 0.37 seconds
GitLint PENDING 0.24 seconds
BuildEll PASS 18.04 seconds
BluezMake PASS 656.02 seconds
MakeCheck PASS 18.46 seconds
MakeDistcheck PASS 225.01 seconds
CheckValgrind PASS 281.58 seconds
CheckSmatch PASS 317.30 seconds
bluezmakeextell PASS 168.76 seconds
IncrementalBuild PENDING 0.24 seconds
ScanBuild PASS 955.62 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-03-09 6:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 4:59 [PATCH BlueZ 0/2] lib/bluetooth/mgmt: Add missing mgmt_op entry for HCI_CMD_SYNC Gabriel Woloz
2026-03-09 4:59 ` [PATCH BlueZ 1/1] lib/bluetooth/mgmt: Added missing command "HCI Cmd Sync" to mgmt_op Gabriel Woloz
2026-03-09 6:21 ` bluez.test.bot [this message]
2026-03-09 14:00 ` [PATCH BlueZ 0/2] lib/bluetooth/mgmt: Add missing mgmt_op entry for HCI_CMD_SYNC patchwork-bot+bluetooth
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=69ae66f4.050a0220.22b4c6.50f5@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=wolozgabriel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox