From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, mariusz.skamra@codecoup.pl
Subject: RE: monitor: Fix truncated server socket path parameter
Date: Wed, 04 Aug 2021 02:39:49 -0700 (PDT) [thread overview]
Message-ID: <610a6065.1c69fb81.c5f80.6121@mx.google.com> (raw)
In-Reply-To: <20210804085937.541076-1-mariusz.skamra@codecoup.pl>
[-- Attachment #1: Type: text/plain, Size: 2734 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=526107
---Test result---
Test Summary:
CheckPatch FAIL 0.39 seconds
GitLint PASS 0.12 seconds
Prep - Setup ELL PASS 46.93 seconds
Build - Prep PASS 0.15 seconds
Build - Configure PASS 8.18 seconds
Build - Make PASS 213.24 seconds
Make Check PASS 9.51 seconds
Make Distcheck PASS 250.91 seconds
Build w/ext ELL - Configure PASS 8.58 seconds
Build w/ext ELL - Make PASS 204.29 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script with rule in .checkpatch.conf
Output:
monitor: Fix truncated server socket path parameter
ERROR:GERRIT_CHANGE_ID: Remove Gerrit Change-Id's before submitting upstream
#11:
Change-Id: I646f86709d59d33b8f1d27b725eb42a9f44f6f2d
- total: 1 errors, 0 warnings, 23 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.
"[PATCH] monitor: Fix truncated server socket path parameter" 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.
##############################
Test: GitLint - PASS
Desc: Run gitlint with rule in .gitlint
##############################
Test: Prep - Setup ELL - PASS
Desc: Clone, build, and install ELL
##############################
Test: Build - Prep - PASS
Desc: Prepare environment for build
##############################
Test: Build - Configure - PASS
Desc: Configure the BlueZ source tree
##############################
Test: Build - Make - PASS
Desc: Build the BlueZ source tree
##############################
Test: Make Check - PASS
Desc: Run 'make check'
##############################
Test: Make Distcheck - PASS
Desc: Run distcheck to check the distribution
##############################
Test: Build w/ext ELL - Configure - PASS
Desc: Configure BlueZ source with '--enable-external-ell' configuration
##############################
Test: Build w/ext ELL - Make - PASS
Desc: Build BlueZ source with '--enable-external-ell' configuration
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2021-08-04 9:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-04 8:59 [PATCH] monitor: Fix truncated server socket path parameter Mariusz Skamra
2021-08-04 9:39 ` bluez.test.bot [this message]
2021-08-04 10:54 ` [PATCH v2] " Mariusz Skamra
2021-08-04 11:30 ` [v2] " bluez.test.bot
2021-08-04 14:53 ` [PATCH v2] " Szymon Janc
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=610a6065.1c69fb81.c5f80.6121@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mariusz.skamra@codecoup.pl \
/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.