From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, pav@iki.fi
Subject: RE: [BlueZ] shared/bap: wait for GATT client ready before ASCS/PACS discovery
Date: Sun, 12 Feb 2023 12:05:39 -0800 (PST) [thread overview]
Message-ID: <63e94693.050a0220.bf91f.1965@mx.google.com> (raw)
In-Reply-To: <98ccef96a4b719599c0fb1d085c7239a12d2ed8c.1676226143.git.pav@iki.fi>
[-- Attachment #1: Type: text/plain, Size: 2438 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=721100
---Test result---
Test Summary:
CheckPatch PASS 0.43 seconds
GitLint FAIL 0.53 seconds
BuildEll PASS 26.40 seconds
BluezMake PASS 787.59 seconds
MakeCheck PASS 11.08 seconds
MakeDistcheck PASS 147.95 seconds
CheckValgrind PASS 241.21 seconds
CheckSmatch PASS 319.48 seconds
bluezmakeextell PASS 95.77 seconds
IncrementalBuild PASS 604.62 seconds
ScanBuild PASS 954.53 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[BlueZ] shared/bap: wait for GATT client ready before ASCS/PACS discovery
WARNING: I3 - ignore-body-lines: gitlint will be switching from using Python regex 'match' (match beginning) to 'search' (match anywhere) semantics. Please review your ignore-body-lines.regex option accordingly. To remove this warning, set general.regex-style-search=True. More details: https://jorisroovers.github.io/gitlint/configuration/#regex-style-search
17: B2 Line has trailing whitespace: " "
60: B1 Line exceeds max length (132>80): " [CHG] Transport /org/bluez/hci0/dev_XX_XX_XX_XX_XX_XX/pac_source0/fd0 Links: /org/bluez/hci0/dev_XX_XX_XX_XX_XX_XX/pac_sink0/fd1"
61: B1 Line exceeds max length (132>80): " [CHG] Transport /org/bluez/hci0/dev_XX_XX_XX_XX_XX_XX/pac_sink0/fd1 Links: /org/bluez/hci0/dev_XX_XX_XX_XX_XX_XX/pac_source0/fd0"
67: B2 Line has trailing whitespace: " "
73: B2 Line has trailing whitespace: " "
75: B2 Line has trailing whitespace: " "
101: B1 Line exceeds max length (132>80): " [CHG] Transport /org/bluez/hci0/dev_XX_XX_XX_XX_XX_XX/pac_source0/fd0 Links: /org/bluez/hci0/dev_XX_XX_XX_XX_XX_XX/pac_sink0/fd1"
102: B1 Line exceeds max length (132>80): " [CHG] Transport /org/bluez/hci0/dev_XX_XX_XX_XX_XX_XX/pac_sink0/fd1 Links: /org/bluez/hci0/dev_XX_XX_XX_XX_XX_XX/pac_source0/fd0"
104: B2 Line has trailing whitespace: " "
106: B2 Line has trailing whitespace: " "
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-02-12 20:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-12 18:34 [PATCH BlueZ] shared/bap: wait for GATT client ready before ASCS/PACS discovery Pauli Virtanen
2023-02-12 20:05 ` bluez.test.bot [this message]
2023-02-12 20:45 ` Luiz Augusto von Dentz
2023-02-12 21:49 ` Pauli Virtanen
2023-02-13 20:40 ` 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=63e94693.050a0220.bf91f.1965@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pav@iki.fi \
/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.