From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, brian.gix@intel.com
Subject: RE: Clean-up stale/unused hci_request.c code
Date: Tue, 26 Jul 2022 17:03:35 -0700 (PDT) [thread overview]
Message-ID: <62e080d7.1c69fb81.343ed.dcf7@mx.google.com> (raw)
In-Reply-To: <20220726230140.205481-2-brian.gix@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1971 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=663264
---Test result---
Test Summary:
CheckPatch FAIL 7.47 seconds
GitLint PASS 3.87 seconds
SubjectPrefix PASS 3.45 seconds
BuildKernel PASS 31.82 seconds
BuildKernel32 PASS 27.62 seconds
Incremental Build with patchesPASS 68.28 seconds
TestRunner: Setup PASS 456.12 seconds
TestRunner: l2cap-tester PASS 16.76 seconds
TestRunner: bnep-tester PASS 6.28 seconds
TestRunner: mgmt-tester PASS 98.34 seconds
TestRunner: rfcomm-tester PASS 9.62 seconds
TestRunner: sco-tester PASS 9.38 seconds
TestRunner: smp-tester PASS 9.51 seconds
TestRunner: userchan-tester PASS 6.91 seconds
Details
##############################
Test: CheckPatch - FAIL - 7.47 seconds
Run checkpatch.pl script with rule in .checkpatch.conf
[v3,4/4] Bluetooth: Convert SCO configure_datapath to hci_sync\CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#128: FILE: net/bluetooth/hci_conn.c:354:
+ err = __hci_cmd_sync_status(hdev, HCI_CONFIGURE_DATA_PATH,
+ sizeof(*cmd) + vnd_len, cmd, HCI_CMD_TIMEOUT);
total: 0 errors, 0 warnings, 1 checks, 200 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/12929916.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
next prev parent reply other threads:[~2022-07-27 0:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 23:01 [PATCH v3 0/4] Clean-up stale/unused hci_request.c code Brian Gix
2022-07-26 23:01 ` [PATCH v3 1/4] Bluetooth: Convert le_scan_disable timeout to hci_sync Brian Gix
2022-07-27 0:03 ` bluez.test.bot [this message]
2022-07-26 23:01 ` [PATCH v3 2/4] Bluetooth: Rework le_scan_restart for hci_sync Brian Gix
2022-07-26 23:01 ` [PATCH v3 3/4] Bluetooth: Delete unused hci_req_stop_discovery() Brian Gix
2022-07-26 23:01 ` [PATCH v3 4/4] Bluetooth: Convert SCO configure_datapath to hci_sync Brian Gix
-- strict thread matches above, loose matches on Subject: below --
2022-08-05 23:42 [PATCH v7 1/9] Bluetooth: Convert le_scan_disable timeout " Brian Gix
2022-08-06 3:06 ` Clean-up stale/unused hci_request.c code bluez.test.bot
2022-08-01 17:14 [PATCH v6 01/10] Bluetooth: Convert le_scan_disable timeout to hci_sync Brian Gix
2022-08-01 18:12 ` Clean-up stale/unused hci_request.c code bluez.test.bot
2022-07-30 0:50 [PATCH v5 01/10] Bluetooth: Convert le_scan_disable timeout to hci_sync Brian Gix
2022-07-30 3:18 ` Clean-up stale/unused hci_request.c code bluez.test.bot
2022-07-27 13:58 [PATCH v4 1/4] Bluetooth: Convert le_scan_disable timeout to hci_sync Brian Gix
2022-07-27 14:30 ` Clean-up stale/unused hci_request.c code bluez.test.bot
2022-07-22 22:20 [PATCH 1/1] Bluetooth: Convert le_scan_disable timeout to hci_sync Brian Gix
2022-07-22 23:08 ` Clean-up stale/unused hci_request.c code bluez.test.bot
2022-07-21 23:22 [PATCH v2 1/3] Bluetooth: Remove dead code from hci_request.c Brian Gix
2022-07-22 0:09 ` Clean-up stale/unused hci_request.c code bluez.test.bot
2022-07-21 22:57 [PATCH 1/3] Bluetooth: Remove dead code from hci_request.c Brian Gix
2022-07-21 23:48 ` Clean-up stale/unused hci_request.c code bluez.test.bot
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=62e080d7.1c69fb81.343ed.dcf7@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=brian.gix@intel.com \
--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.