From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, pav@iki.fi
Subject: RE: [BlueZ,v2..,1/3] lib: tools: remove POLL_ERRQUEUE
Date: Mon, 14 Jul 2025 11:14:19 -0700 (PDT) [thread overview]
Message-ID: <687548fb.050a0220.2c7ec1.33d0@mx.google.com> (raw)
In-Reply-To: <2ffec6539fe38318c713b48985aaddda9671f258.1752511478.git.pav@iki.fi>
[-- 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=982161
---Test result---
Test Summary:
CheckPatch PENDING 0.34 seconds
GitLint PENDING 0.28 seconds
BuildEll PASS 20.47 seconds
BluezMake PASS 2663.57 seconds
MakeCheck PASS 20.16 seconds
MakeDistcheck PASS 186.55 seconds
CheckValgrind PASS 235.33 seconds
CheckSmatch PASS 308.40 seconds
bluezmakeextell PASS 129.17 seconds
IncrementalBuild PENDING 0.22 seconds
ScanBuild PASS 932.27 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-07-14 18:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 16:44 [PATCH BlueZ v2.. 1/3] lib: tools: remove POLL_ERRQUEUE Pauli Virtanen
2025-07-14 16:44 ` [PATCH BlueZ v2.. 2/3] lib: add BT_PKT_SEQNUM and BT_SCM_PKT_SEQNUM Pauli Virtanen
2025-07-14 16:44 ` [PATCH BlueZ v2.. 3/3] iso-tester: add tests for BT_PKT_SEQNUM Pauli Virtanen
2025-07-14 18:14 ` bluez.test.bot [this message]
2025-07-14 21:00 ` [PATCH BlueZ v2.. 1/3] lib: tools: remove POLL_ERRQUEUE 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=687548fb.050a0220.2c7ec1.33d0@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pav@iki.fi \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.