All of lore.kernel.org
 help / color / mirror / Atom feed
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: Tue, 04 Jul 2023 02:15:34 -0700 (PDT)	[thread overview]
Message-ID: <64a3e336.050a0220.760a9.7427@mx.google.com> (raw)
In-Reply-To: <20230704074144.5587-2-claudia.rosu@nxp.com>

[-- Attachment #1: Type: text/plain, Size: 1659 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=762233

---Test result---

Test Summary:
CheckPatch                    PASS      0.51 seconds
GitLint                       PASS      0.34 seconds
BuildEll                      PASS      26.52 seconds
BluezMake                     PASS      782.29 seconds
MakeCheck                     PASS      11.23 seconds
MakeDistcheck                 PASS      155.31 seconds
CheckValgrind                 PASS      250.03 seconds
CheckSmatch                   WARNING   334.74 seconds
bluezmakeextell               PASS      101.71 seconds
IncrementalBuild              PASS      651.12 seconds
ScanBuild                     WARNING   1007.16 seconds

Details
##############################
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


  reply	other threads:[~2023-07-04  9:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-04  7:41 [PATCH BlueZ v2 0/1] monitor: Add decoding support for Sync Receiver events Claudia Draghicescu
2023-07-04  7:41 ` [PATCH BlueZ v2 1/1] " Claudia Draghicescu
2023-07-04  9:15   ` bluez.test.bot [this message]
2023-07-05 18:00 ` [PATCH BlueZ v2 0/1] " patchwork-bot+bluetooth
  -- strict thread matches above, loose matches on Subject: below --
2023-07-03 13:43 [PATCH BlueZ 1/1] " Claudia Draghicescu
2023-07-03 15:10 ` 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=64a3e336.050a0220.760a9.7427@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.