From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, hadess@hadess.net
Subject: RE: [BlueZ,v4,1/6] adapter: Keep track of whether the adapter is rfkill'ed
Date: Wed, 31 Aug 2022 03:23:15 -0700 (PDT) [thread overview]
Message-ID: <630f3693.c80a0220.658dc.628a@mx.google.com> (raw)
In-Reply-To: <20220831091912.47894-1-hadess@hadess.net>
[-- Attachment #1: Type: text/plain, Size: 4502 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=672764
---Test result---
Test Summary:
CheckPatch FAIL 9.12 seconds
GitLint PASS 6.06 seconds
Prep - Setup ELL PASS 31.33 seconds
Build - Prep PASS 0.88 seconds
Build - Configure PASS 10.02 seconds
Build - Make PASS 941.21 seconds
Make Check PASS 12.27 seconds
Make Check w/Valgrind PASS 338.64 seconds
Make Distcheck PASS 277.34 seconds
Build w/ext ELL - Configure PASS 10.07 seconds
Build w/ext ELL - Make PASS 97.46 seconds
Incremental Build w/ patches PASS 702.02 seconds
Scan Build PASS 736.92 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script with rule in .checkpatch.conf
Output:
[BlueZ,v4,1/6] adapter: Keep track of whether the adapter is rfkill'ed
ERROR:CODE_INDENT: code indent should use tabs where possible
#95: FILE: src/adapter.c:7558:
+^I g_dbus_emit_property_changed(dbus_conn, adapter->path,$
ERROR:CODE_INDENT: code indent should use tabs where possible
#110: FILE: src/adapter.c:7574:
+^I g_dbus_emit_property_changed(dbus_conn, adapter->path,$
/github/workspace/src/12960589.patch total: 2 errors, 0 warnings, 90 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.
NOTE: Whitespace errors detected.
You may wish to use scripts/cleanpatch or scripts/cleanfile
/github/workspace/src/12960589.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.
[BlueZ,v4,2/6] adapter: Implement PowerState property
ERROR:CODE_INDENT: code indent should use tabs where possible
#96: FILE: src/adapter.c:590:
+^I g_dbus_emit_property_changed(dbus_conn, adapter->path,$
WARNING:LONG_LINE: line length of 97 exceeds 80 columns
#123: FILE: src/adapter.c:659:
+ reset_power_state_target(adapter, settings & MGMT_SETTING_POWERED ? 0x01 : 0x00);
WARNING:LONG_LINE_STRING: line length of 81 exceeds 80 columns
#153: FILE: src/adapter.c:727:
+ ADAPTER_INTERFACE, "PowerState");
WARNING:LONG_LINE_STRING: line length of 81 exceeds 80 columns
#175: FILE: src/adapter.c:761:
+ ADAPTER_INTERFACE, "PowerState");
WARNING:LONG_LINE_STRING: line length of 81 exceeds 80 columns
#209: FILE: src/adapter.c:3101:
+ ADAPTER_INTERFACE, "PowerState");
WARNING:LONG_LINE_STRING: line length of 81 exceeds 80 columns
#222: FILE: src/adapter.c:3115:
+ ADAPTER_INTERFACE, "PowerState");
WARNING:LONG_LINE: line length of 84 exceeds 80 columns
#239: FILE: src/adapter.c:3156:
+ } else if (adapter->power_state_target == ADAPTER_POWER_STATE_TARGET_NONE) {
WARNING:LONG_LINE: line length of 81 exceeds 80 columns
#245: FILE: src/adapter.c:3162:
+ if (adapter->power_state_target == ADAPTER_POWER_STATE_TARGET_ON)
WARNING:LONG_LINE_STRING: line length of 81 exceeds 80 columns
#273: FILE: src/adapter.c:5620:
+ ADAPTER_INTERFACE, "PowerState");
WARNING:LONG_LINE_STRING: line length of 81 exceeds 80 columns
#282: FILE: src/adapter.c:7365:
+ ADAPTER_INTERFACE, "PowerState");
/github/workspace/src/12960593.patch total: 1 errors, 9 warnings, 197 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.
NOTE: Whitespace errors detected.
You may wish to use scripts/cleanpatch or scripts/cleanfile
/github/workspace/src/12960593.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
next prev parent reply other threads:[~2022-08-31 10:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 9:19 [PATCH BlueZ v4 1/6] adapter: Keep track of whether the adapter is rfkill'ed Bastien Nocera
2022-08-31 9:19 ` [PATCH BlueZ v4 2/6] adapter: Implement PowerState property Bastien Nocera
2022-08-31 20:03 ` Luiz Augusto von Dentz
2022-09-01 10:43 ` Bastien Nocera
2022-08-31 9:19 ` [PATCH BlueZ v4 3/6] client: Print the " Bastien Nocera
2022-08-31 9:19 ` [PATCH BlueZ v4 4/6] adapter-api: Add PowerState property documentation Bastien Nocera
2022-08-31 9:19 ` [PATCH BlueZ v4 5/6] adapter: Fix typo in function name Bastien Nocera
2022-08-31 9:19 ` [PATCH BlueZ v4 6/6] adapter: Remove experimental flag for PowerState Bastien Nocera
2022-08-31 9:23 ` Bastien Nocera
2022-08-31 10:23 ` bluez.test.bot [this message]
2022-08-31 11:36 ` [BlueZ,v4,1/6] adapter: Keep track of whether the adapter is rfkill'ed Bastien Nocera
2022-08-31 11:36 ` [PATCH BlueZ v4 1/6] " Bastien Nocera
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=630f3693.c80a0220.658dc.628a@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 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.