From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, hadess@hadess.net
Subject: RE: [BlueZ,v6,1/6] adapter: Keep track of whether the adapter is rfkill'ed
Date: Thu, 01 Sep 2022 04:32:09 -0700 (PDT) [thread overview]
Message-ID: <63109839.020a0220.3f6f9.9259@mx.google.com> (raw)
In-Reply-To: <20220901104331.174588-1-hadess@hadess.net>
[-- Attachment #1: Type: text/plain, Size: 2744 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=673181
---Test result---
Test Summary:
CheckPatch FAIL 6.85 seconds
GitLint PASS 4.57 seconds
Prep - Setup ELL PASS 26.48 seconds
Build - Prep PASS 0.70 seconds
Build - Configure PASS 8.06 seconds
Build - Make PASS 714.85 seconds
Make Check PASS 11.37 seconds
Make Check w/Valgrind PASS 284.31 seconds
Make Distcheck PASS 232.78 seconds
Build w/ext ELL - Configure PASS 8.10 seconds
Build w/ext ELL - Make PASS 81.59 seconds
Incremental Build w/ patches PASS 578.06 seconds
Scan Build PASS 585.92 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script with rule in .checkpatch.conf
Output:
[BlueZ,v6,2/6] adapter: Implement PowerState property
WARNING:LONG_LINE: line length of 81 exceeds 80 columns
#137: FILE: src/adapter.c:659:
+static void reset_power_state_target(struct btd_adapter *adapter, uint32_t value)
WARNING:LONG_LINE: line length of 90 exceeds 80 columns
#177: FILE: src/adapter.c:714:
+ adapter_set_power_state(adapter, ADAPTER_POWER_STATE_OFF_BLOCKED);
WARNING:LONG_LINE: line length of 82 exceeds 80 columns
#191: FILE: src/adapter.c:758:
+ ADAPTER_POWER_STATE_OFF_ENABLING :
WARNING:LONG_LINE: line length of 82 exceeds 80 columns
#192: FILE: src/adapter.c:759:
+ ADAPTER_POWER_STATE_ON_DISABLING);
WARNING:LONG_LINE: line length of 90 exceeds 80 columns
#233: FILE: src/adapter.c:3025:
+ adapter_set_power_state(adapter, ADAPTER_POWER_STATE_OFF_BLOCKED);
WARNING:LONG_LINE: line length of 86 exceeds 80 columns
#326: FILE: src/adapter.c:6830:
+ DBG("Power state: %s", adapter_power_state_str(adapter->power_state));
/github/workspace/src/12962285.patch total: 0 errors, 6 warnings, 278 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/12962285.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.
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2022-09-01 11:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 10:43 [PATCH BlueZ v6 1/6] adapter: Keep track of whether the adapter is rfkill'ed Bastien Nocera
2022-09-01 10:43 ` [PATCH BlueZ v6 2/6] adapter: Implement PowerState property Bastien Nocera
2022-09-01 10:43 ` [PATCH BlueZ v6 3/6] client: Print the " Bastien Nocera
2022-09-01 10:43 ` [PATCH BlueZ v6 4/6] adapter-api: Add PowerState property documentation Bastien Nocera
2022-09-01 10:43 ` [PATCH BlueZ v6 5/6] adapter: Fix typo in function name Bastien Nocera
2022-09-01 10:43 ` [PATCH BlueZ v6 6/6] adapter: Remove experimental flag for PowerState Bastien Nocera
2022-09-01 11:07 ` [PATCH BlueZ v6 1/6] adapter: Keep track of whether the adapter is rfkill'ed Bastien Nocera
2022-09-01 11:32 ` 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=63109839.020a0220.3f6f9.9259@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