From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, pav@iki.fi
Subject: RE: [BlueZ,v2] client: fix ISO send data rate
Date: Sat, 11 May 2024 10:43:38 -0700 (PDT) [thread overview]
Message-ID: <663fae4a.d40a0220.5e590.96ac@mx.google.com> (raw)
In-Reply-To: <30fd803be62f762706486698821e9e5fff2d0b63.1715442270.git.pav@iki.fi>
[-- Attachment #1: Type: text/plain, Size: 1482 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=852558
---Test result---
Test Summary:
CheckPatch PASS 0.45 seconds
GitLint FAIL 0.48 seconds
BuildEll PASS 24.55 seconds
BluezMake PASS 1719.88 seconds
MakeCheck PASS 13.12 seconds
MakeDistcheck PASS 176.82 seconds
CheckValgrind PASS 251.27 seconds
CheckSmatch PASS 353.65 seconds
bluezmakeextell PASS 120.99 seconds
IncrementalBuild PASS 1503.96 seconds
ScanBuild PASS 1033.85 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[BlueZ,v2] client: fix ISO send data rate
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
22: B2 Line has trailing whitespace: " "
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2024-05-11 17:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-11 15:45 [PATCH BlueZ v2] client: fix ISO send data rate Pauli Virtanen
2024-05-11 17:43 ` bluez.test.bot [this message]
2024-05-13 14:10 ` patchwork-bot+bluetooth
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=663fae4a.d40a0220.5e590.96ac@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.