From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,1/6] settings: Add btd_settings_gatt_db_{store,load}
Date: Wed, 18 May 2022 19:33:13 -0700 (PDT) [thread overview]
Message-ID: <6285ac69.1c69fb81.597fc.7653@mx.google.com> (raw)
In-Reply-To: <20220518221701.2220062-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4166 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=642899
---Test result---
Test Summary:
CheckPatch FAIL 7.67 seconds
GitLint PASS 2.82 seconds
Prep - Setup ELL PASS 51.73 seconds
Build - Prep PASS 0.64 seconds
Build - Configure PASS 10.19 seconds
Build - Make PASS 1707.88 seconds
Make Check PASS 12.58 seconds
Make Check w/Valgrind PASS 528.47 seconds
Make Distcheck PASS 288.81 seconds
Build w/ext ELL - Configure PASS 10.30 seconds
Build w/ext ELL - Make PASS 1702.73 seconds
Incremental Build with patchesPASS 10363.18 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script with rule in .checkpatch.conf
Output:
[BlueZ,4/6] monitor: Move ATT decoding function into its own file
WARNING:SPACING: Unnecessary space before function pointer arguments
#618: FILE: monitor/att.c:501:
+ void (*func) (const struct l2cap_frame *frame);
ERROR:SPACING: space prohibited before that ',' (ctx:WxE)
#657: FILE: monitor/att.c:540:
+ { 0x12, "Write Request" ,
^
/github/workspace/src/12854194.patch total: 1 errors, 1 warnings, 1316 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/12854194.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,5/6] monitor: Cache connection information
WARNING:TYPO_SPELLING: 'addres' may be misspelled - perhaps 'address'?
#82:
This caches connection information including the device addres so it can
^^^^^^
WARNING:SPACING: Unnecessary space before function pointer arguments
#3958: FILE: monitor/packet.c:8833:
+ void (*cmd_func) (uint16_t index, const void *data, uint8_t size);
WARNING:SPACING: Unnecessary space before function pointer arguments
#3962: FILE: monitor/packet.c:8836:
+ void (*rsp_func) (uint16_t index, const void *data, uint8_t size);
WARNING:SPACING: Unnecessary space before function pointer arguments
#4943: FILE: monitor/packet.c:11433:
+ void (*func) (uint16_t index, const void *data, uint8_t size);
WARNING:SPACING: Unnecessary space before function pointer arguments
#5001: FILE: monitor/packet.c:11617:
+ void (*func) (uint16_t index, const void *data, uint8_t size);
WARNING:SPACING: Unnecessary space before function pointer arguments
#5055: FILE: monitor/vendor.h:17:
+ void (*cmd_func) (uint16_t index, const void *data, uint8_t size);
WARNING:SPACING: Unnecessary space before function pointer arguments
#5059: FILE: monitor/vendor.h:20:
+ void (*rsp_func) (uint16_t index, const void *data, uint8_t size);
WARNING:SPACING: Unnecessary space before function pointer arguments
#5068: FILE: monitor/vendor.h:28:
+ void (*evt_func) (uint16_t index, const void *data, uint8_t size);
/github/workspace/src/12854196.patch total: 0 errors, 8 warnings, 4552 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/12854196.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-05-19 2:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 22:16 [PATCH BlueZ 1/6] settings: Add btd_settings_gatt_db_{store,load} Luiz Augusto von Dentz
2022-05-18 22:16 ` [PATCH BlueZ 2/6] gatt: Store local GATT database Luiz Augusto von Dentz
2022-05-18 22:16 ` [PATCH BlueZ 3/6] monitor: Move print_hex_field to display.h Luiz Augusto von Dentz
2022-05-18 22:16 ` [PATCH BlueZ 4/6] monitor: Move ATT decoding function into its own file Luiz Augusto von Dentz
2022-05-18 22:17 ` [PATCH BlueZ 5/6] monitor: Cache connection information Luiz Augusto von Dentz
2022-05-18 22:17 ` [PATCH BlueZ 6/6] monitor/att: Decode attribute type Luiz Augusto von Dentz
2022-05-19 2:33 ` 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=6285ac69.1c69fb81.597fc.7653@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 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.