From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, pav@iki.fi
Subject: RE: [BlueZ,1/2] shared: mainloop: Skip removed mainloop events
Date: Sun, 27 Sep 2026 14:14:47 -0700 (PDT) [thread overview]
Message-ID: <6ab98747.f3e70d7f.7867e.7423@mx.google.com> (raw)
In-Reply-To: <fc1baff935104e08b170f528477e31bfedc57c7c.1790531371.git.pav@iki.fi>
[-- Attachment #1: Type: text/plain, Size: 2273 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/series/1174578/
---Test result---
Test Summary:
CheckPatch FAIL 1.13 seconds
GitLint FAIL 0.68 seconds
BuildEll PASS 19.09 seconds
BluezMake PASS 381.66 seconds
MakeCheck PASS 14.33 seconds
MakeDistcheck PASS 137.22 seconds
CheckValgrind PASS 227.86 seconds
CheckSmatch PASS 284.89 seconds
bluezmakeextell PASS 92.27 seconds
TestFunctional PASS 1082.60 seconds
IncrementalBuild PASS 406.78 seconds
ScanBuild PASS 1103.09 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,1/2] shared: mainloop: Skip removed mainloop events
WARNING:COMMIT_LOG_LONG_LINE: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#96:
#1 0x5637f7b41f79 in mainloop_run_with_signal src/shared/mainloop-notify.c:196
/home/runner/work/bluez/bluez/src/patch/14849970.patch total: 0 errors, 1 warnings, 48 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
/home/runner/work/bluez/bluez/src/patch/14849970.patch has style problems, please review.
NOTE: Ignored message types: COMMIT_MESSAGE COMPLEX_MACRO CONST_STRUCT FILE_PATH_CHANGES MISSING_SIGN_OFF PREFER_PACKED SPDX_LICENSE_TAG SPLIT_STRING SSCANF_TO_KSTRTO
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[BlueZ,1/2] shared: mainloop: Skip removed mainloop events
18: B1 Line exceeds max length (82>80): " #1 0x5637f7b41f79 in mainloop_run_with_signal src/shared/mainloop-notify.c:196"
https://github.com/bluez/bluez/pull/2597
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-09-27 21:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-27 17:49 [PATCH BlueZ 1/2] shared: mainloop: Skip removed mainloop events Pauli Virtanen
2026-09-27 17:49 ` [PATCH BlueZ 2/2] unit: test-mainloop: add basic mainloop test Pauli Virtanen
2026-09-27 21:14 ` bluez.test.bot [this message]
2026-09-28 17:50 ` [PATCH BlueZ 1/2] shared: mainloop: Skip removed mainloop events 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=6ab98747.f3e70d7f.7867e.7423@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.