From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,v3,1/4] profiles/gap: Some code cleanup
Date: Fri, 10 May 2024 10:54:24 -0700 (PDT) [thread overview]
Message-ID: <663e5f50.170a0220.b5100.9e06@mx.google.com> (raw)
In-Reply-To: <20240510150938.1492169-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1867 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=852343
---Test result---
Test Summary:
CheckPatch FAIL 1.57 seconds
GitLint PASS 0.81 seconds
BuildEll PASS 24.18 seconds
BluezMake PASS 1646.05 seconds
MakeCheck PASS 13.67 seconds
MakeDistcheck PASS 173.75 seconds
CheckValgrind PASS 244.10 seconds
CheckSmatch PASS 346.75 seconds
bluezmakeextell PASS 117.90 seconds
IncrementalBuild PASS 6038.21 seconds
ScanBuild PASS 966.73 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,v3,1/4] profiles/gap: Some code cleanup
WARNING:TYPO_SPELLING: 'unecessary' may be misspelled - perhaps 'unnecessary'?
#91:
Just removing unecessary function and code duplication.
^^^^^^^^^^
/github/workspace/src/src/13661723.patch total: 0 errors, 1 warnings, 89 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/13661723.patch has style problems, please review.
NOTE: Ignored message types: COMMIT_MESSAGE COMPLEX_MACRO CONST_STRUCT FILE_PATH_CHANGES MISSING_SIGN_OFF PREFER_PACKED SPDX_LICENSE_TAG SPLIT_STRING SSCANF_TO_KSTRTO
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:[~2024-05-10 17:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 15:09 [PATCH BlueZ v3 1/4] profiles/gap: Some code cleanup Luiz Augusto von Dentz
2024-05-10 15:09 ` [PATCH BlueZ v3 2/4] src/adapter: Added connection parameter load/store functions Luiz Augusto von Dentz
2024-05-10 15:09 ` [PATCH BlueZ v3 3/4] src/device: Added function to set connection parameters Luiz Augusto von Dentz
2024-05-10 15:09 ` [PATCH BlueZ v3 4/4] profiles/gap: Added support for PPCP characteristic Luiz Augusto von Dentz
2024-05-10 16:50 ` [PATCH BlueZ v3 1/4] profiles/gap: Some code cleanup patchwork-bot+bluetooth
2024-05-10 17:54 ` 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=663e5f50.170a0220.b5100.9e06@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).