From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, josephsih@chromium.org
Subject: RE: [BlueZ,v6,1/8] doc: Introduce the quality report command and event
Date: Thu, 26 May 2022 08:39:38 -0700 (PDT) [thread overview]
Message-ID: <628f9f3a.1c69fb81.49317.594e@mx.google.com> (raw)
In-Reply-To: <20220526112456.2488536-1-josephsih@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 1323 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=645249
---Test result---
Test Summary:
CheckPatch PASS 8.83 seconds
GitLint FAIL 5.88 seconds
Prep - Setup ELL PASS 43.76 seconds
Build - Prep PASS 0.56 seconds
Build - Configure PASS 8.53 seconds
Build - Make PASS 1334.80 seconds
Make Check PASS 11.63 seconds
Make Check w/Valgrind PASS 458.89 seconds
Make Distcheck PASS 239.06 seconds
Build w/ext ELL - Configure PASS 8.89 seconds
Build w/ext ELL - Make PASS 1320.90 seconds
Incremental Build with patchesPASS 10678.68 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint with rule in .gitlint
Output:
[BlueZ,v6,2/8] lib: Add structures and constants for quality report command and event
1: T1 Title exceeds max length (85>80): "[BlueZ,v6,2/8] lib: Add structures and constants for quality report command and event"
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-05-26 15:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 11:24 [BlueZ PATCH v6 1/8] doc: Introduce the quality report command and event Joseph Hwang
2022-05-26 11:24 ` [BlueZ PATCH v6 2/8] lib: Add structures and constants for " Joseph Hwang
2022-05-26 11:24 ` [BlueZ PATCH v6 3/8] adapter: remove quality report from experimental features Joseph Hwang
2022-05-26 20:31 ` Luiz Augusto von Dentz
2022-05-27 3:13 ` Joseph Hwang
2022-05-30 21:02 ` Luiz Augusto von Dentz
2022-05-26 11:24 ` [BlueZ PATCH v6 4/8] adapter: support AOSP MGMT_EV_QUALITY_REPORT Joseph Hwang
2022-05-26 11:24 ` [BlueZ PATCH v6 5/8] adapter: support Intel MGMT_EV_QUALITY_REPORT Joseph Hwang
2022-05-26 11:24 ` [BlueZ PATCH v6 6/8] tools/btmgmt: fix quality report command Joseph Hwang
2022-05-26 11:24 ` [BlueZ PATCH v6 7/8] monitor: print quality report cmd Joseph Hwang
2022-05-26 11:24 ` [BlueZ PATCH v6 8/8] monitor: packet: add missing decodings of MGMT commands to todo Joseph Hwang
2022-05-26 15:39 ` bluez.test.bot [this message]
2022-06-02 16:00 ` [BlueZ PATCH v6 1/8] doc: Introduce the quality report command and event patchwork-bot+bluetooth
2022-06-07 6:40 ` Joseph Hwang
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=628f9f3a.1c69fb81.49317.594e@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=josephsih@chromium.org \
--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 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.