From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, simon.mikuda@streamunlimited.com
Subject: RE: l2test: Enable hex input for PSM
Date: Mon, 27 Mar 2023 23:57:04 -0700 (PDT) [thread overview]
Message-ID: <64228fc0.d40a0220.43ef1.c3fa@mx.google.com> (raw)
In-Reply-To: <20230328052619.1357253-2-simon.mikuda@streamunlimited.com>
[-- Attachment #1: Type: text/plain, Size: 2017 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=734449
---Test result---
Test Summary:
CheckPatch FAIL 1.32 seconds
GitLint PASS 0.68 seconds
BuildEll PASS 27.26 seconds
BluezMake PASS 1033.05 seconds
MakeCheck PASS 11.60 seconds
MakeDistcheck PASS 153.92 seconds
CheckValgrind PASS 251.46 seconds
CheckSmatch PASS 335.56 seconds
bluezmakeextell PASS 101.56 seconds
IncrementalBuild PASS 1774.04 seconds
ScanBuild PASS 1067.84 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,v2,2/2] l2test: Fix setting mode for BR/EDR l2cap socket
ERROR:SWITCH_CASE_INDENT_LEVEL: switch and case should be at the same indent
#110: FILE: tools/l2test.c:160:
+ switch (mode) {
+ case BT_MODE_BASIC:
[...]
+ case BT_MODE_ERTM:
[...]
+ case BT_MODE_STREAMING:
[...]
+ case BT_MODE_LE_FLOWCTL:
[...]
+ case BT_MODE_EXT_FLOWCTL:
[...]
+ default:
/github/workspace/src/src/13190513.patch total: 1 errors, 0 warnings, 44 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/13190513.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:[~2023-03-28 6:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 10:27 [PATCH BlueZ 0/2] l2test fix+feature Simon Mikuda
2023-03-23 10:27 ` [PATCH BlueZ 1/2] l2test: Enable hex input for PSM Simon Mikuda
2023-03-23 11:42 ` l2test fix+feature bluez.test.bot
2023-03-23 17:20 ` [PATCH BlueZ 1/2] l2test: Enable hex input for PSM Luiz Augusto von Dentz
2023-03-28 5:26 ` [PATCH BlueZ v2 0/2] " Simon Mikuda
2023-03-28 5:26 ` [PATCH BlueZ v2 1/2] " Simon Mikuda
2023-03-28 6:57 ` bluez.test.bot [this message]
2023-03-28 5:26 ` [PATCH BlueZ v2 2/2] l2test: Fix setting mode for BR/EDR l2cap socket Simon Mikuda
2023-03-28 20:50 ` [PATCH BlueZ v2 0/2] l2test: Enable hex input for PSM patchwork-bot+bluetooth
2023-03-23 10:27 ` [PATCH BlueZ 2/2] l2test: Fix setting mode for BR/EDR l2cap socket Simon Mikuda
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=64228fc0.d40a0220.43ef1.c3fa@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=simon.mikuda@streamunlimited.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.