From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, wangyouwan@uniontech.com
Subject: RE: bluez:fix btmon tools “Allow slave” to "Master Or Slave" #431 [hci0] 99.922927
Date: Wed, 21 Jul 2021 20:02:06 -0700 (PDT) [thread overview]
Message-ID: <60f8dfae.1c69fb81.db54d.e55d@mx.google.com> (raw)
In-Reply-To: <20210722021952.18260-1-wangyouwan@uniontech.com>
[-- Attachment #1: Type: text/plain, Size: 3569 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=519397
---Test result---
Test Summary:
CheckPatch FAIL 0.26 seconds
GitLint FAIL 0.11 seconds
Prep - Setup ELL PASS 40.07 seconds
Build - Prep PASS 0.09 seconds
Build - Configure PASS 6.91 seconds
Build - Make PASS 173.73 seconds
Make Check PASS 8.95 seconds
Make Distcheck PASS 205.55 seconds
Build w/ext ELL - Configure PASS 7.04 seconds
Build w/ext ELL - Make PASS 163.65 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script with rule in .checkpatch.conf
Output:
bluez:fix btmon tools “Allow slave” to "Master Or Slave" #431 [hci0] 99.922927
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#11:
I want to explain it as “Master Or Slave”, because this is explained in the Core_v5.2
- total: 0 errors, 1 warnings, 8 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] =?UTF-8?q?bluez:fix=20btmon=20tools=20=E2=80=9CAllow=20sl?=" 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 - FAIL
Desc: Run gitlint with rule in .gitlint
Output:
bluez:fix btmon tools “Allow slave” to "Master Or Slave" #431 [hci0] 99.922927
1: T1 Title exceeds max length (78>72): "bluez:fix btmon tools “Allow slave” to "Master Or Slave" #431 [hci0] 99.922927"
3: B1 Line exceeds max length (85>80): "I want to explain it as “Master Or Slave”, because this is explained in the Core_v5.2"
8: B1 Line exceeds max length (83>80): " joining an existing piconet, since by definition the paging device is initially"
11: B1 Line exceeds max length (86>80): " • A role switch is necessary in order for a slave in an existing piconet to set up"
12: B1 Line exceeds max length (81>80): " a new piconet with itself as master and the original piconet master as slave."
##############################
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-22 3:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-22 2:19 [PATCH] bluez:fix btmon tools “Allow slave” to "Master Or Slave" #431 [hci0] 99.922927 wangyouwan
2021-07-22 3:02 ` bluez.test.bot [this message]
2021-07-22 7:07 ` Barry Byford
2021-07-22 14:47 ` Marcel Holtmann
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=60f8dfae.1c69fb81.db54d.e55d@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=wangyouwan@uniontech.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 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.