From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, claudia.rosu@nxp.com
Subject: RE: monitor: Add decoding support for Sync Receiver events
Date: Mon, 03 Jul 2023 08:10:29 -0700 (PDT) [thread overview]
Message-ID: <64a2e4e5.050a0220.b9559.7bc6@mx.google.com> (raw)
In-Reply-To: <20230703134341.13312-2-claudia.rosu@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 2263 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=762038
---Test result---
Test Summary:
CheckPatch PASS 0.49 seconds
GitLint FAIL 0.56 seconds
BuildEll PASS 26.60 seconds
BluezMake PASS 791.65 seconds
MakeCheck PASS 12.01 seconds
MakeDistcheck PASS 155.99 seconds
CheckValgrind PASS 250.96 seconds
CheckSmatch WARNING 338.29 seconds
bluezmakeextell PASS 101.81 seconds
IncrementalBuild PASS 654.72 seconds
ScanBuild WARNING 1016.91 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[BlueZ,1/1] monitor: Add decoding support for Sync Receiver events
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
3: B2 Line has trailing whitespace: "This commit adds decoding support for PA Sync Established, "
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
monitor/packet.c: note: in included file:monitor/display.h:82:26: warning: Variable length array is used.monitor/packet.c:1832:26: warning: Variable length array is used.monitor/packet.c: note: in included file:monitor/bt.h:3552:52: warning: array of flexible structuresmonitor/bt.h:3540:40: warning: array of flexible structures
##############################
Test: ScanBuild - WARNING
Desc: Run Scan Build
Output:
monitor/packet.c:12370:2: warning: Null pointer passed to 2nd parameter expecting 'nonnull'
memcpy(tx, tv, sizeof(*tv));
^~~~~~~~~~~~~~~~~~~~~~~~~~~
1 warning generated.
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-07-03 15:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 13:43 [PATCH BlueZ 0/1] monitor: Add decoding support for Sync Receiver events Claudia Draghicescu
2023-07-03 13:43 ` [PATCH BlueZ 1/1] " Claudia Draghicescu
2023-07-03 15:10 ` bluez.test.bot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-04 7:41 [PATCH BlueZ v2 " Claudia Draghicescu
2023-07-04 9:15 ` 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=64a2e4e5.050a0220.b9559.7bc6@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=claudia.rosu@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.