From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, hadess@hadess.net
Subject: RE: Port text docs to RST and move man pages
Date: Thu, 22 Jan 2026 02:07:17 -0800 (PST) [thread overview]
Message-ID: <6971f6d5.050a0220.6771.af19@mx.google.com> (raw)
In-Reply-To: <20260122091003.398400-2-hadess@hadess.net>
[-- Attachment #1: Type: text/plain, Size: 1262 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=1045561
---Test result---
Test Summary:
CheckPatch PENDING 0.39 seconds
GitLint PENDING 0.41 seconds
BuildEll PASS 20.04 seconds
BluezMake PASS 645.56 seconds
MakeCheck PASS 18.65 seconds
MakeDistcheck PASS 242.83 seconds
CheckValgrind PASS 292.26 seconds
CheckSmatch PASS 352.60 seconds
bluezmakeextell PASS 185.14 seconds
IncrementalBuild PENDING 0.38 seconds
ScanBuild PASS 1028.74 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-01-22 10:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 9:04 [BlueZ v3 0/9] Port text docs to RST and move man pages Bastien Nocera
2026-01-22 9:05 ` [BlueZ v3 1/9] doc: Rename section 7 " Bastien Nocera
2026-01-22 10:07 ` bluez.test.bot [this message]
2026-01-22 9:05 ` [BlueZ v3 2/9] doc: Move all the man pages to doc/ Bastien Nocera
2026-01-22 9:57 ` Bastien Nocera
2026-01-22 9:05 ` [BlueZ v3 3/9] doc: Port assigned-numbers.txt to RST Bastien Nocera
2026-01-22 9:05 ` [BlueZ v3 4/9] doc: Port thermometer-api.txt " Bastien Nocera
2026-01-22 9:05 ` [BlueZ v3 5/9] doc: Port security-bugs.txt " Bastien Nocera
2026-01-22 9:05 ` [BlueZ v3 6/9] doc: Port coding-style.txt " Bastien Nocera
2026-01-22 9:05 ` [BlueZ v3 7/9] doc: Port sap-api.txt " Bastien Nocera
2026-01-22 9:05 ` [BlueZ v3 8/9] doc: Port maintainer-guidelines.txt " Bastien Nocera
2026-01-22 9:05 ` [BlueZ v3 9/9] doc: Port health-api.txt " Bastien Nocera
2026-01-22 16:50 ` [BlueZ v3 0/9] Port text docs to RST and move man pages 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=6971f6d5.050a0220.6771.af19@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=hadess@hadess.net \
--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