From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,v1] isotest: Fix not handling 0 length packets
Date: Tue, 23 Jan 2024 08:32:13 -0800 (PST) [thread overview]
Message-ID: <65afea0d.a70a0220.fcd73.eb72@mx.google.com> (raw)
In-Reply-To: <20240123152850.2880226-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1850 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=819152
---Test result---
Test Summary:
CheckPatch FAIL 0.61 seconds
GitLint PASS 0.23 seconds
BuildEll PASS 24.01 seconds
BluezMake PASS 720.96 seconds
MakeCheck PASS 11.97 seconds
MakeDistcheck PASS 166.30 seconds
CheckValgrind PASS 228.76 seconds
CheckSmatch PASS 344.76 seconds
bluezmakeextell PASS 112.21 seconds
IncrementalBuild PASS 690.32 seconds
ScanBuild PASS 955.84 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,v1] isotest: Fix not handling 0 length packets
WARNING:TYPO_SPELLING: 'sucess' may be misspelled - perhaps 'success'?
#92:
means their status is not sucess.
^^^^^^
/github/workspace/src/src/13527607.patch total: 0 errors, 1 warnings, 16 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/13527607.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
next prev parent reply other threads:[~2024-01-23 16:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 15:28 [PATCH BlueZ v1] isotest: Fix not handling 0 length packets Luiz Augusto von Dentz
2024-01-23 16:32 ` bluez.test.bot [this message]
2024-01-23 18:41 ` patchwork-bot+bluetooth
-- strict thread matches above, loose matches on Subject: below --
2024-01-23 15:28 Luiz Augusto von Dentz
2024-01-23 16:32 ` [BlueZ,v1] " 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=65afea0d.a70a0220.fcd73.eb72@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 NNTP newsgroup(s).