From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, i.kamaletdinov@omp.ru
Subject: RE: Fix few more bugs found by SVACE
Date: Sat, 07 May 2022 13:00:14 -0700 (PDT) [thread overview]
Message-ID: <6276cfce.1c69fb81.36b6e.704d@mx.google.com> (raw)
In-Reply-To: <20220507170703.29902-2-i.kamaletdinov@omp.ru>
[-- Attachment #1: Type: text/plain, Size: 1960 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=639427
---Test result---
Test Summary:
CheckPatch FAIL 5.66 seconds
GitLint PASS 3.95 seconds
Prep - Setup ELL PASS 42.99 seconds
Build - Prep PASS 0.68 seconds
Build - Configure PASS 8.64 seconds
Build - Make PASS 1360.55 seconds
Make Check PASS 11.83 seconds
Make Check w/Valgrind PASS 444.92 seconds
Make Distcheck PASS 230.71 seconds
Build w/ext ELL - Configure PASS 8.64 seconds
Build w/ext ELL - Make PASS 1380.96 seconds
Incremental Build with patchesPASS 5642.52 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script with rule in .checkpatch.conf
Output:
[BlueZ,1/4] tools: Fix memory leak in hciconfig
ERROR:TRAILING_WHITESPACE: trailing whitespace
#68: FILE: tools/hciconfig.c:84:
+^I$
/github/workspace/src/12842099.patch total: 1 errors, 0 warnings, 12 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/12842099.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:[~2022-05-07 20:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-07 17:06 [PATCH BlueZ 0/4] [v2] Fix few more bugs found by SVACE Ildar Kamaletdinov
2022-05-07 17:07 ` [PATCH BlueZ 1/4] tools: Fix memory leak in hciconfig Ildar Kamaletdinov
2022-05-07 20:00 ` bluez.test.bot [this message]
2022-05-07 17:07 ` [PATCH BlueZ 2/4] tools: Fix memory leaks in btgatt-server/client Ildar Kamaletdinov
2022-05-07 17:07 ` [PATCH BlueZ 3/4] tools: Fix handle leak in rfcomm Ildar Kamaletdinov
2022-05-07 17:07 ` [PATCH BlueZ 4/4] device: Fix uninitialized value usage Ildar Kamaletdinov
-- strict thread matches above, loose matches on Subject: below --
2022-05-07 17:35 [PATCH BlueZ 1/4] tools: Fix memory leak in hciconfig Ildar Kamaletdinov
2022-05-07 20:16 ` Fix few more bugs found by SVACE bluez.test.bot
2022-05-07 15:06 [PATCH BlueZ 1/4] tools: Fix memory leak in hciconfig Ildar Kamaletdinov
2022-05-07 17:53 ` Fix few more bugs found by SVACE 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=6276cfce.1c69fb81.36b6e.704d@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=i.kamaletdinov@omp.ru \
--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 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).