From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, yuran.pereira@hotmail.com
Subject: RE: Bluetooth: Add documentation and replace printk calls
Date: Mon, 06 Nov 2023 15:00:59 -0800 (PST) [thread overview]
Message-ID: <6549702b.920a0220.42548.3976@mx.google.com> (raw)
In-Reply-To: <DB3PR10MB68355F5AE036ABD128F91535E8AAA@DB3PR10MB6835.EURPRD10.PROD.OUTLOOK.COM>
[-- Attachment #1: Type: text/plain, Size: 2322 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=799231
---Test result---
Test Summary:
CheckPatch FAIL 1.54 seconds
GitLint PASS 0.59 seconds
SubjectPrefix PASS 0.18 seconds
BuildKernel PASS 32.85 seconds
CheckAllWarning PASS 35.98 seconds
CheckSparse PASS 41.19 seconds
CheckSmatch PASS 116.09 seconds
BuildKernel32 PASS 32.19 seconds
TestRunnerSetup PASS 502.42 seconds
TestRunner_l2cap-tester PASS 29.45 seconds
TestRunner_iso-tester PASS 53.84 seconds
TestRunner_bnep-tester PASS 10.02 seconds
TestRunner_mgmt-tester PASS 203.88 seconds
TestRunner_rfcomm-tester PASS 15.10 seconds
TestRunner_sco-tester PASS 18.24 seconds
TestRunner_ioctl-tester PASS 16.98 seconds
TestRunner_mesh-tester PASS 12.28 seconds
TestRunner_smp-tester PASS 13.22 seconds
TestRunner_userchan-tester PASS 10.21 seconds
IncrementalBuild PASS 34.94 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[1/2] Bluetooth: Add documentation to exported functions in lib
WARNING: please, no space before tabs
#121: FILE: net/bluetooth/lib.c:36:
+ * ^I^I bd address.$
ERROR: trailing whitespace
#142: FILE: net/bluetooth/lib.c:60:
+ * Return: $
total: 1 errors, 1 warnings, 0 checks, 125 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/src/13447550.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:[~2023-11-06 23:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 22:21 [PATCH 0/2] Bluetooth: Add documentation and replace printk calls Yuran Pereira
2023-11-06 22:24 ` [PATCH 1/2] Bluetooth: Add documentation to exported functions in lib Yuran Pereira
2023-11-06 23:00 ` bluez.test.bot [this message]
2023-11-06 22:26 ` [PATCH 2/2] Bluetooth: Replaces printk with pr_debug in bt_dbg Yuran Pereira
2023-11-07 6:31 ` Greg KH
2023-11-07 16:02 ` Yuran Pereira
2023-11-07 18:13 ` Greg KH
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=6549702b.920a0220.42548.3976@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=yuran.pereira@hotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox