From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, sonnysasaka@chromium.org
Subject: RE: [BlueZ] monitor: Print EIR of Extended Advertisement Report
Date: Wed, 14 Jul 2021 18:26:10 -0700 (PDT) [thread overview]
Message-ID: <60ef8eb2.1c69fb81.6fb78.9241@mx.google.com> (raw)
In-Reply-To: <20210715003521.2222-1-sonnysasaka@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 2732 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=515781
---Test result---
Test Summary:
CheckPatch FAIL 0.24 seconds
GitLint PASS 0.11 seconds
Prep - Setup ELL PASS 39.40 seconds
Build - Prep PASS 0.09 seconds
Build - Configure PASS 7.11 seconds
Build - Make PASS 170.91 seconds
Make Check PASS 8.82 seconds
Make Distcheck PASS 204.00 seconds
Build w/ext ELL - Configure PASS 6.98 seconds
Build w/ext ELL - Make PASS 161.16 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script with rule in .checkpatch.conf
Output:
monitor: Print EIR of Extended Advertisement Report
ERROR:GERRIT_CHANGE_ID: Remove Gerrit Change-Id's before submitting upstream
#9:
Change-Id: I4805e589837733e7ecf9d33218e4135e8f822a7c
- total: 1 errors, 0 warnings, 7 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: Print EIR of Extended Advertisement Report" 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-07-15 1:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-15 0:35 [PATCH BlueZ] monitor: Print EIR of Extended Advertisement Report Sonny Sasaka
2021-07-15 1:26 ` bluez.test.bot [this message]
2021-07-29 17:51 ` [BlueZ] " Sonny Sasaka
2021-07-29 21:21 ` Luiz Augusto von Dentz
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=60ef8eb2.1c69fb81.6fb78.9241@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=sonnysasaka@chromium.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).