From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, ruc_gongyuanjun@163.com
Subject: RE: [1/1] Bluetooth: hci_uart: check for missing tty operations
Date: Wed, 06 Apr 2022 22:12:45 -0700 (PDT) [thread overview]
Message-ID: <624e72cd.1c69fb81.ce944.910f@mx.google.com> (raw)
In-Reply-To: <20220407042623.28438-1-ruc_gongyuanjun@163.com>
[-- Attachment #1: Type: text/plain, Size: 4221 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=629800
---Test result---
Test Summary:
CheckPatch FAIL 1.93 seconds
GitLint PASS 0.95 seconds
SubjectPrefix PASS 0.86 seconds
BuildKernel PASS 31.00 seconds
BuildKernel32 PASS 27.28 seconds
Incremental Build with patchesPASS 37.94 seconds
TestRunner: Setup PASS 477.97 seconds
TestRunner: l2cap-tester PASS 15.85 seconds
TestRunner: bnep-tester PASS 6.11 seconds
TestRunner: mgmt-tester PASS 102.09 seconds
TestRunner: rfcomm-tester PASS 7.70 seconds
TestRunner: sco-tester PASS 7.64 seconds
TestRunner: smp-tester PASS 7.56 seconds
TestRunner: userchan-tester PASS 6.21 seconds
Details
##############################
Test: CheckPatch - FAIL - 1.93 seconds
Run checkpatch.pl script with rule in .checkpatch.conf
[1/1] Bluetooth: hci_uart: check for missing tty operations\ERROR:CODE_INDENT: code indent should use tabs where possible
#76: FILE: drivers/bluetooth/hci_ag6xx.c:39:
+ if (!hci_uart_has_flow_control(hu))$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#76: FILE: drivers/bluetooth/hci_ag6xx.c:39:
+ if (!hci_uart_has_flow_control(hu))$
WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (8, 12)
#76: FILE: drivers/bluetooth/hci_ag6xx.c:39:
+ if (!hci_uart_has_flow_control(hu))
+ return -EOPNOTSUPP;
ERROR:CODE_INDENT: code indent should use tabs where possible
#77: FILE: drivers/bluetooth/hci_ag6xx.c:40:
+ return -EOPNOTSUPP;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#77: FILE: drivers/bluetooth/hci_ag6xx.c:40:
+ return -EOPNOTSUPP;$
ERROR:CODE_INDENT: code indent should use tabs where possible
#90: FILE: drivers/bluetooth/hci_h4.c:47:
+ if (!hci_uart_has_flow_control(hu))$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#90: FILE: drivers/bluetooth/hci_h4.c:47:
+ if (!hci_uart_has_flow_control(hu))$
WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (8, 12)
#90: FILE: drivers/bluetooth/hci_h4.c:47:
+ if (!hci_uart_has_flow_control(hu))
+ return -EOPNOTSUPP;
ERROR:CODE_INDENT: code indent should use tabs where possible
#91: FILE: drivers/bluetooth/hci_h4.c:48:
+ return -EOPNOTSUPP;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#91: FILE: drivers/bluetooth/hci_h4.c:48:
+ return -EOPNOTSUPP;$
ERROR:CODE_INDENT: code indent should use tabs where possible
#104: FILE: drivers/bluetooth/hci_ll.c:117:
+ if (!hci_uart_has_flow_control(hu))$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#104: FILE: drivers/bluetooth/hci_ll.c:117:
+ if (!hci_uart_has_flow_control(hu))$
WARNING:SUSPECT_CODE_INDENT: suspect code indent for conditional statements (8, 12)
#104: FILE: drivers/bluetooth/hci_ll.c:117:
+ if (!hci_uart_has_flow_control(hu))
+ return -EOPNOTSUPP;
ERROR:CODE_INDENT: code indent should use tabs where possible
#105: FILE: drivers/bluetooth/hci_ll.c:118:
+ return -EOPNOTSUPP;$
WARNING:LEADING_SPACE: please, no spaces at the start of a line
#105: FILE: drivers/bluetooth/hci_ll.c:118:
+ return -EOPNOTSUPP;$
total: 6 errors, 9 warnings, 27 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/12804440.patch has style problems, please review.
NOTE: Ignored message types: UNKNOWN_COMMIT_ID
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-04-07 5:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 4:26 [PATCH 1/1] Bluetooth: hci_uart: check for missing tty operations Yuanjun Gong
2022-04-07 5:12 ` 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=624e72cd.1c69fb81.ce944.910f@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=ruc_gongyuanjun@163.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.