From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, arthur@marmottus.net
Subject: RE: Expose the disconnect reason over D-Bus
Date: Mon, 12 Dec 2022 06:41:09 -0800 (PST) [thread overview]
Message-ID: <63973d85.050a0220.8dafe.e30d@mx.google.com> (raw)
In-Reply-To: <20221212133235.79657-2-arthur@marmottus.net>
[-- Attachment #1: Type: text/plain, Size: 1994 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=703845
---Test result---
Test Summary:
CheckPatch FAIL 0.79 seconds
GitLint PASS 0.34 seconds
BuildEll PASS 27.63 seconds
BluezMake PASS 1018.21 seconds
MakeCheck PASS 11.85 seconds
MakeDistcheck PASS 149.74 seconds
CheckValgrind PASS 247.21 seconds
bluezmakeextell PASS 97.21 seconds
IncrementalBuild PASS 855.05 seconds
ScanBuild PASS 1064.30 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,1/1] device: Expose the disconnect reason over D-Bus
WARNING:LONG_LINE: line length of 81 exceeds 80 columns
#98: FILE: src/device.c:2640:
+static void btd_device_disconnected_cb(struct btd_device *device, uint8_t reason)
WARNING:LONG_LINE: line length of 84 exceeds 80 columns
#113: FILE: src/device.c:3011:
+ { "DisconnectReason", "y", dev_property_get_disconnect_reason, NULL, NULL },
/github/workspace/src/src/13071144.patch total: 0 errors, 2 warnings, 67 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/src/13071144.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-12-12 14:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 13:32 [PATCH BlueZ 0/1] Expose the disconnect reason over D-Bus Arthur Crepin-Leblond
2022-12-12 13:32 ` [PATCH BlueZ 1/1] device: " Arthur Crepin-Leblond
2022-12-12 14:41 ` bluez.test.bot [this message]
2022-12-12 14:49 ` [PATCH BlueZ 0/1] " Bastien Nocera
2022-12-12 15:36 ` Arthur Crepin-Leblond
2022-12-13 20:45 ` Luiz Augusto von Dentz
2022-12-20 12:30 ` Arthur Crepin-Leblond
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=63973d85.050a0220.8dafe.e30d@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=arthur@marmottus.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