From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,v1,1/4] btio: Handle EOPNOTSUPP from accept() to prevent busy loop
Date: Tue, 09 Jun 2026 12:35:25 -0700 (PDT) [thread overview]
Message-ID: <6a286afd.965034cc.1d2e75.364b@mx.google.com> (raw)
In-Reply-To: <20260609165057.90837-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1909 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=1108736
---Test result---
Test Summary:
CheckPatch FAIL 1.15 seconds
GitLint PASS 0.80 seconds
BuildEll PASS 20.44 seconds
BluezMake PASS 680.07 seconds
MakeCheck PASS 18.48 seconds
MakeDistcheck PASS 247.78 seconds
CheckValgrind PASS 292.15 seconds
CheckSmatch PASS 353.17 seconds
bluezmakeextell PASS 182.48 seconds
IncrementalBuild PASS 692.42 seconds
ScanBuild PASS 1037.61 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,v1,4/4] bearer: Check btd_opts.mode on btd_bearer_new
WARNING:LONG_LINE: line length of 81 exceeds 80 columns
#126: FILE: src/bearer.c:283:
+ (type != BDADDR_BREDR && btd_opts.mode == BT_MODE_BREDR))
/github/workspace/src/patch/14620165.patch total: 0 errors, 1 warnings, 17 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.
/github/workspace/src/patch/14620165.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.
https://github.com/bluez/bluez/pull/2203
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-06-09 19:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 16:50 [PATCH BlueZ v1 1/4] btio: Handle EOPNOTSUPP from accept() to prevent busy loop Luiz Augusto von Dentz
2026-06-09 16:50 ` [PATCH BlueZ v1 2/4] profile: Check if bearer is enabled on registration Luiz Augusto von Dentz
2026-06-09 16:50 ` [PATCH BlueZ v1 3/4] plugins: Check btd_profile_register return value Luiz Augusto von Dentz
2026-06-09 16:50 ` [PATCH BlueZ v1 4/4] bearer: Check btd_opts.mode on btd_bearer_new Luiz Augusto von Dentz
2026-06-09 19:35 ` 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=6a286afd.965034cc.1d2e75.364b@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
/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