From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, ayaanmirza.788@gmail.com
Subject: RE: Bluetooth: bfusb: Updated code to follow style guide
Date: Fri, 08 Mar 2024 08:43:53 -0800 (PST) [thread overview]
Message-ID: <65eb4049.050a0220.b0e71.849d@mx.google.com> (raw)
In-Reply-To: <20240308162037.100226-1-ayaanmirza.788@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2806 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=833841
---Test result---
Test Summary:
CheckPatch FAIL 0.89 seconds
GitLint FAIL 0.48 seconds
SubjectPrefix PASS 0.11 seconds
BuildKernel PASS 27.03 seconds
CheckAllWarning PASS 29.71 seconds
CheckSparse PASS 34.77 seconds
CheckSmatch PASS 96.15 seconds
BuildKernel32 PASS 26.14 seconds
TestRunnerSetup PASS 492.94 seconds
TestRunner_l2cap-tester PASS 17.63 seconds
TestRunner_iso-tester PASS 29.65 seconds
TestRunner_bnep-tester PASS 4.62 seconds
TestRunner_mgmt-tester PASS 105.66 seconds
TestRunner_rfcomm-tester PASS 7.06 seconds
TestRunner_sco-tester PASS 14.70 seconds
TestRunner_ioctl-tester PASS 7.52 seconds
TestRunner_mesh-tester PASS 5.61 seconds
TestRunner_smp-tester PASS 7.15 seconds
TestRunner_userchan-tester PASS 4.76 seconds
IncrementalBuild PASS 25.17 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
Bluetooth: bfusb: Updated code to follow style guide
WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#93:
Added indendations, removed trailing spaces, added empty lines after declaration.
total: 0 errors, 1 warnings, 31 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/13587034.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:
Bluetooth: bfusb: Updated code to follow style guide
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
3: B1 Line exceeds max length (81>80): "Added indendations, removed trailing spaces, added empty lines after declaration."
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2024-03-08 16:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 16:20 [PATCH] Bluetooth: bfusb: Updated code to follow style guide Ayaan Mirza Baig
2024-03-08 16:43 ` bluez.test.bot [this message]
2024-03-08 18:03 ` [PATCH] Bluetooth: bfusb: corrected mistakes in previous commits Ayaan Mirza Baig
2024-03-08 18:26 ` bluez.test.bot
2024-03-08 18:08 ` [PATCH] Bluetooth: bfusb: Updated code to follow style guide Joe Perches
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=65eb4049.050a0220.b0e71.849d@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=ayaanmirza.788@gmail.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.