From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, hadess@hadess.net
Subject: RE: build: Add meson build system
Date: Wed, 08 Oct 2025 05:17:32 -0700 (PDT) [thread overview]
Message-ID: <68e6565c.050a0220.126044.cae2@mx.google.com> (raw)
In-Reply-To: <20251008104132.2206963-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=1009338
---Test result---
Test Summary:
CheckPatch PENDING 0.31 seconds
GitLint PENDING 0.30 seconds
BuildEll PASS 19.92 seconds
BluezMake PASS 2675.00 seconds
MakeCheck PASS 19.91 seconds
MakeDistcheck PASS 182.81 seconds
CheckValgrind PASS 235.15 seconds
CheckSmatch PASS 306.36 seconds
bluezmakeextell PASS 127.95 seconds
IncrementalBuild PENDING 0.30 seconds
ScanBuild PASS 907.15 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:[~2025-10-08 12:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-08 10:40 [PATCH BlueZ v3 00/10] build: Add meson build system Bastien Nocera
2025-10-08 10:40 ` [PATCH BlueZ v3 01/10] build: Add meson wrap for libell Bastien Nocera
2025-10-08 12:17 ` bluez.test.bot [this message]
2025-10-08 10:40 ` [PATCH BlueZ v3 02/10] build: Add meson build system Bastien Nocera
2025-10-08 10:40 ` [PATCH BlueZ v3 03/10] build: Make more use of 'feature' options Bastien Nocera
2025-10-08 10:40 ` [PATCH BlueZ v3 04/10] build: Separate systemd and libsystemd dependencies Bastien Nocera
2025-10-08 10:40 ` [PATCH BlueZ v3 05/10] tools: Install gatttool if deprecated tools are enabled Bastien Nocera
2025-10-08 10:40 ` [PATCH BlueZ v3 06/10] tools: Install avinfo tool by default Bastien Nocera
2025-10-08 10:40 ` [PATCH BlueZ v3 07/10] tools: Install btmgmt along with other tools Bastien Nocera
2025-10-08 10:40 ` [PATCH BlueZ v3 08/10] emulator: Install the emulator if built Bastien Nocera
2025-10-08 10:40 ` [PATCH BlueZ v3 09/10] build: Add option to allow disabling bluetoothd Bastien Nocera
2025-10-08 10:40 ` [PATCH BlueZ v3 10/10] build: Add License field to pkg-config file Bastien Nocera
2025-10-08 10:50 ` [BlueZ,v3,10/10] " bluez.test.bot
-- strict thread matches above, loose matches on Subject: below --
2025-10-13 8:32 [PATCH BlueZ v5 1/9] build: Add meson wrap for libell Bastien Nocera
2025-10-13 10:15 ` build: Add meson build system bluez.test.bot
2025-10-09 10:33 [PATCH BlueZ v4 01/10] build: Add meson wrap for libell Bastien Nocera
2025-10-09 12:19 ` build: Add meson build system bluez.test.bot
2025-10-08 8:40 [PATCH BlueZ v2 1/9] build: Add meson wrap for libell Bastien Nocera
2025-10-08 10:34 ` build: Add meson build system bluez.test.bot
2025-08-11 19:53 [PATCH BlueZ 1/8] build: Add ell subproject Bastien Nocera
2025-08-11 21:39 ` build: Add meson build system 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=68e6565c.050a0220.126044.cae2@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