From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, hadess@hadess.net
Subject: RE: Port text docs to RST
Date: Tue, 20 Jan 2026 08:59:04 -0800 (PST) [thread overview]
Message-ID: <696fb458.050a0220.1af079.9a30@mx.google.com> (raw)
In-Reply-To: <20260120160811.3394320-2-hadess@hadess.net>
[-- Attachment #1: Type: text/plain, Size: 1531 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=1044766
---Test result---
Test Summary:
CheckPatch PENDING 0.38 seconds
GitLint PENDING 0.32 seconds
BuildEll PASS 17.83 seconds
BluezMake PASS 654.90 seconds
MakeCheck PASS 17.79 seconds
MakeDistcheck FAIL 6.61 seconds
CheckValgrind PASS 280.22 seconds
CheckSmatch PASS 318.18 seconds
bluezmakeextell PASS 168.22 seconds
IncrementalBuild PENDING 0.36 seconds
ScanBuild PASS 925.08 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
Test: MakeDistcheck - FAIL
Desc: Run Bluez Make Distcheck
Output:
make[2]: *** No rule to make target 'doc/sap-api.txt', needed by 'distdir-am'. Stop.
make[1]: *** [Makefile:10870: distdir] Error 2
make: *** [Makefile:10946: dist] Error 2
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-01-20 16:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 16:05 [BlueZ 0/7] Port text docs to RST Bastien Nocera
2026-01-20 16:05 ` [BlueZ 1/7] doc: Port assigned-numbers.txt " Bastien Nocera
2026-01-20 16:59 ` bluez.test.bot [this message]
2026-01-20 16:05 ` [BlueZ 2/7] doc: Port thermometer-api.txt " Bastien Nocera
2026-01-20 16:05 ` [BlueZ 3/7] doc: Port security-bugs.txt " Bastien Nocera
2026-01-20 16:05 ` [BlueZ 4/7] doc: Port coding-style.txt " Bastien Nocera
2026-01-20 16:05 ` [BlueZ 5/7] doc: Port sap-api.txt " Bastien Nocera
2026-01-20 16:05 ` [BlueZ 6/7] doc: Port maintainer-guidelines.txt " Bastien Nocera
2026-01-20 16:05 ` [BlueZ 7/7] doc: Port health-api.txt " Bastien Nocera
-- strict thread matches above, loose matches on Subject: below --
2026-01-20 17:18 [BlueZ v2 1/7] doc: Port assigned-numbers.txt " Bastien Nocera
2026-01-20 18:34 ` Port text docs " 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=696fb458.050a0220.1af079.9a30@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