From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, iulia.tanasescu@nxp.com
Subject: RE: monitor/att: Add decoding support for BASS
Date: Tue, 04 Apr 2023 08:31:10 -0700 (PDT) [thread overview]
Message-ID: <642c42be.5e0a0220.58122.32d2@mx.google.com> (raw)
In-Reply-To: <20230404143053.101464-2-iulia.tanasescu@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 1791 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=736846
---Test result---
Test Summary:
CheckPatch PASS 0.79 seconds
GitLint FAIL 0.70 seconds
BuildEll PASS 26.74 seconds
BluezMake PASS 758.73 seconds
MakeCheck PASS 11.53 seconds
MakeDistcheck PASS 149.92 seconds
CheckValgrind PASS 242.62 seconds
CheckSmatch WARNING 329.06 seconds
bluezmakeextell PASS 98.21 seconds
IncrementalBuild PASS 617.07 seconds
ScanBuild PASS 988.58 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[BlueZ,1/1] monitor/att: Add decoding support for BASS
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
12: B3 Line contains hard tab characters (\t): " 68020101000000000403020400"
33: B2 Line has trailing whitespace: " Value: "
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
monitor/att.c: note: in included file:monitor/display.h:82:26: warning: Variable length array is used.
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-04-04 15:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 14:30 [PATCH BlueZ 0/1] monitor/att: Add decoding support for BASS Iulia Tanasescu
2023-04-04 14:30 ` [PATCH BlueZ 1/1] " Iulia Tanasescu
2023-04-04 15:31 ` bluez.test.bot [this message]
2023-04-04 18:13 ` Luiz Augusto von Dentz
2023-04-05 11:46 ` Iulia Tanasescu
-- strict thread matches above, loose matches on Subject: below --
2023-04-05 10:54 [PATCH BlueZ v2 " Iulia Tanasescu
2023-04-05 12:21 ` bluez.test.bot
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=642c42be.5e0a0220.58122.32d2@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=iulia.tanasescu@nxp.com \
--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.