From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, frederic.danis@collabora.com
Subject: RE: [BlueZ,1/3] tools/btpclient: Move btpclient to client/btpclient directory
Date: Mon, 16 Feb 2026 09:53:50 -0800 (PST) [thread overview]
Message-ID: <699359ae.050a0220.b0b47.0198@mx.google.com> (raw)
In-Reply-To: <20260216165127.110686-1-frederic.danis@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 1964 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=1054634
---Test result---
Test Summary:
CheckPatch PENDING 0.44 seconds
GitLint PENDING 0.39 seconds
BuildEll PASS 20.97 seconds
BluezMake PASS 670.34 seconds
MakeCheck PASS 19.24 seconds
MakeDistcheck FAIL 43.54 seconds
CheckValgrind PASS 297.77 seconds
CheckSmatch PASS 363.94 seconds
bluezmakeextell PASS 188.31 seconds
IncrementalBuild PENDING 0.36 seconds
ScanBuild PASS 1059.02 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:
../../client/btpclient/core.c:14:10: fatal error: btpclient.h: No such file or directory
14 | #include "btpclient.h"
| ^~~~~~~~~~~~~
compilation terminated.
make[2]: *** [Makefile:7170: client/btpclient/core.o] Error 1
make[2]: *** Waiting for unfinished jobs....
../../client/btpclient/gap.c:20:10: fatal error: btpclient.h: No such file or directory
20 | #include "btpclient.h"
| ^~~~~~~~~~~~~
compilation terminated.
make[2]: *** [Makefile:7170: client/btpclient/gap.o] Error 1
make[1]: *** [Makefile:4218: all] Error 2
make: *** [Makefile:10818: distcheck] Error 1
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-02-16 17:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 16:51 [PATCH BlueZ 1/3] tools/btpclient: Move btpclient to client/btpclient directory Frédéric Danis
2026-02-16 16:51 ` [PATCH BlueZ 2/3] client/btpclient: Move btp core service in its own file Frédéric Danis
2026-02-16 16:51 ` [PATCH BlueZ 3/3] client/btpclient: Move btp GAP " Frédéric Danis
2026-02-16 17:53 ` bluez.test.bot [this message]
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=699359ae.050a0220.b0b47.0198@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=frederic.danis@collabora.com \
--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