From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, neeraj.sanjaykale@nxp.com
Subject: RE: Add support for NXP bluetooth chipsets
Date: Mon, 30 Jan 2023 10:35:51 -0800 (PST) [thread overview]
Message-ID: <63d80e07.020a0220.c8278.909c@mx.google.com> (raw)
In-Reply-To: <20230130180504.2029440-2-neeraj.sanjaykale@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 5987 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=717061
---Test result---
Test Summary:
CheckPatch FAIL 4.92 seconds
GitLint FAIL 1.21 seconds
SubjectPrefix FAIL 0.57 seconds
BuildKernel PASS 32.32 seconds
CheckAllWarning PASS 34.84 seconds
CheckSparse PASS 39.59 seconds
CheckSmatch PASS 109.75 seconds
BuildKernel32 PASS 30.92 seconds
TestRunnerSetup PASS 432.43 seconds
TestRunner_l2cap-tester PASS 16.18 seconds
TestRunner_iso-tester PASS 16.69 seconds
TestRunner_bnep-tester PASS 5.44 seconds
TestRunner_mgmt-tester PASS 107.72 seconds
TestRunner_rfcomm-tester PASS 8.74 seconds
TestRunner_sco-tester PASS 7.93 seconds
TestRunner_ioctl-tester PASS 9.32 seconds
TestRunner_mesh-tester PASS 6.77 seconds
TestRunner_smp-tester PASS 7.81 seconds
TestRunner_userchan-tester PASS 5.73 seconds
IncrementalBuild PASS 36.31 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[v2,1/3] serdev: Add method to assert break
WARNING: ENOTSUPP is not a SUSV4 error code, prefer EOPNOTSUPP
#126: FILE: drivers/tty/serdev/core.c:413:
+ return -ENOTSUPP;
WARNING: ENOTSUPP is not a SUSV4 error code, prefer EOPNOTSUPP
#149: FILE: drivers/tty/serdev/serdev-ttyport.c:256:
+ return -ENOTSUPP;
WARNING: function definition argument 'struct serdev_controller *' should also have an identifier name
#173: FILE: include/linux/serdev.h:95:
+ int (*break_ctl)(struct serdev_controller *, unsigned int);
WARNING: function definition argument 'unsigned int' should also have an identifier name
#173: FILE: include/linux/serdev.h:95:
+ int (*break_ctl)(struct serdev_controller *, unsigned int);
WARNING: function definition argument 'struct serdev_device *' should also have an identifier name
#181: FILE: include/linux/serdev.h:206:
+int serdev_device_break_ctl(struct serdev_device *, int);
WARNING: function definition argument 'int' should also have an identifier name
#181: FILE: include/linux/serdev.h:206:
+int serdev_device_break_ctl(struct serdev_device *, int);
WARNING: ENOTSUPP is not a SUSV4 error code, prefer EOPNOTSUPP
#191: FILE: include/linux/serdev.h:262:
+ return -ENOTSUPP;
total: 0 errors, 7 warnings, 65 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/13121548.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.
[v2,3/3] Bluetooth: NXP: Add protocol support for NXP Bluetooth chipsets
WARNING: MAINTAINERS entries use one tab after TYPE:
#171: FILE: MAINTAINERS:22843:
+F: drivers/bluetooth/btnxpuart*
WARNING: line length of 102 exceeds 100 columns
#257: FILE: drivers/bluetooth/btnxpuart.c:45:
+ u32 plen, void *param)
WARNING: line length of 101 exceeds 100 columns
#656: FILE: drivers/bluetooth/btnxpuart.c:444:
+ (char *)&uart_config,
WARNING: line length of 106 exceeds 100 columns
#657: FILE: drivers/bluetooth/btnxpuart.c:445:
+ sizeof(uart_config) - 4));
WARNING: line length of 103 exceeds 100 columns
#677: FILE: drivers/bluetooth/btnxpuart.c:465:
+ sizeof(nxp_cmd7) - 4));
WARNING: Missing a blank line after declarations
#691: FILE: drivers/bluetooth/btnxpuart.c:479:
+ struct nxp_bootloader_cmd *hdr = (struct nxp_bootloader_cmd *)buf;
+ return __le32_to_cpu(hdr->payload_len);
WARNING: Block comments should align the * on each line
#745: FILE: drivers/bluetooth/btnxpuart.c:533:
+ /* The CRC did not match at the other end.
+ * That's why the request to re-send.
WARNING: Block comments should align the * on each line
#752: FILE: drivers/bluetooth/btnxpuart.c:540:
+ /* The FW bin file is made up of many blocks of
+ * 16 byte header and payload data chunks. If the
WARNING: Block comments should align the * on each line
#763: FILE: drivers/bluetooth/btnxpuart.c:551:
+ /* All OK here. Increment offset by number
+ * of previous successfully sent bytes.
total: 0 errors, 9 warnings, 1401 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/13121550.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.
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[v2,2/3] dt-bindings: net: bluetooth: Add NXP bluetooth support
WARNING: I3 - ignore-body-lines: gitlint will be switching from using Python regex 'match' (match beginning) to 'search' (match anywhere) semantics. Please review your ignore-body-lines.regex option accordingly. To remove this warning, set general.regex-style-search=True. More details: https://jorisroovers.github.io/gitlint/configuration/#regex-style-search
15: B1 Line exceeds max length (86>80): " create mode 100644 Documentation/devicetree/bindings/net/bluetooth/nxp-bluetooth.yaml"
##############################
Test: SubjectPrefix - FAIL
Desc: Check subject contains "Bluetooth" prefix
Output:
"Bluetooth: " prefix is not specified in the subject
"Bluetooth: " prefix is not specified in the subject
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-01-30 18:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 18:05 [PATCH v2 0/3] Add support for NXP bluetooth chipsets Neeraj Sanjay Kale
2023-01-30 18:05 ` [PATCH v2 1/3] serdev: Add method to assert break Neeraj Sanjay Kale
2023-01-30 18:35 ` bluez.test.bot [this message]
2023-01-31 8:57 ` Leon Romanovsky
2023-01-31 9:50 ` Greg KH
2023-01-30 18:05 ` [PATCH v2 2/3] dt-bindings: net: bluetooth: Add NXP bluetooth support Neeraj Sanjay Kale
2023-01-31 1:52 ` Rob Herring
2023-01-31 19:04 ` Krzysztof Kozlowski
2023-01-30 18:05 ` [PATCH v2 3/3] Bluetooth: NXP: Add protocol support for NXP Bluetooth chipsets Neeraj Sanjay Kale
2023-01-30 21:10 ` Luiz Augusto von Dentz
2023-01-31 2:20 ` Rob Herring
2023-02-01 12:33 ` Neeraj sanjay kale
2023-01-31 9:01 ` Leon Romanovsky
2023-01-31 10:00 ` Ilpo Järvinen
-- strict thread matches above, loose matches on Subject: below --
2023-03-16 17:22 [PATCH v13 1/4] serdev: Replace all instances of ENOTSUPP with EOPNOTSUPP Neeraj Sanjay Kale
2023-03-16 18:36 ` Add support for NXP bluetooth chipsets bluez.test.bot
2023-03-15 12:03 [PATCH v12 1/4] serdev: Replace all instances of ENOTSUPP with EOPNOTSUPP Neeraj Sanjay Kale
2023-03-15 12:42 ` Add support for NXP bluetooth chipsets bluez.test.bot
2023-03-14 15:32 [PATCH v11 1/4] serdev: Replace all instances of ENOTSUPP with EOPNOTSUPP Neeraj Sanjay Kale
2023-03-14 16:03 ` Add support for NXP bluetooth chipsets bluez.test.bot
2023-03-13 14:40 [PATCH v10 1/3] serdev: Add method to assert break signal over tty UART port Neeraj Sanjay Kale
2023-03-13 15:33 ` Add support for NXP bluetooth chipsets bluez.test.bot
2023-03-13 14:09 [PATCH v9 1/3] serdev: Add method to assert break signal over tty UART port Neeraj Sanjay Kale
2023-03-13 14:33 ` Add support for NXP bluetooth chipsets bluez.test.bot
2023-03-10 18:19 [PATCH v8 1/3] serdev: Add method to assert break signal over tty UART port Neeraj Sanjay Kale
2023-03-10 19:03 ` Add support for NXP bluetooth chipsets bluez.test.bot
2023-03-06 17:05 [PATCH v7 1/3] serdev: Add method to assert break signal over tty UART port Neeraj Sanjay Kale
2023-03-06 17:33 ` Add support for NXP bluetooth chipsets bluez.test.bot
2023-03-01 15:45 [PATCH v6 1/3] serdev: Add method to assert break signal over tty UART port Neeraj Sanjay Kale
2023-03-01 16:38 ` Add support for NXP bluetooth chipsets bluez.test.bot
2023-02-23 10:36 [PATCH v5 1/3] serdev: Add method to assert break signal over tty UART port Neeraj Sanjay Kale
2023-02-23 11:01 ` Add support for NXP bluetooth chipsets bluez.test.bot
2023-02-21 16:25 [PATCH v4 1/3] serdev: Add method to assert break signal over tty UART port Neeraj Sanjay Kale
2023-02-21 17:10 ` Add support for NXP bluetooth chipsets bluez.test.bot
2023-02-13 14:54 [PATCH v3 1/3] serdev: Add method to assert break signal over tty UART port Neeraj Sanjay Kale
2023-02-13 15:40 ` Add support for NXP bluetooth chipsets bluez.test.bot
2023-01-24 17:47 [PATCH v1 1/3] serdev: Add method to assert break Neeraj Sanjay Kale
2023-01-24 18:38 ` Add support for NXP bluetooth chipsets 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=63d80e07.020a0220.c8278.909c@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=neeraj.sanjaykale@nxp.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.