All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,v3,1/5] monitor: Add TX frame number and speed estimation
Date: Tue, 01 Aug 2023 20:21:05 -0700 (PDT)	[thread overview]
Message-ID: <64c9cba1.170a0220.f573e.95ab@mx.google.com> (raw)
In-Reply-To: <20230801233135.537864-1-luiz.dentz@gmail.com>

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

---Test result---

Test Summary:
CheckPatch                    FAIL      2.29 seconds
GitLint                       PASS      1.16 seconds
BuildEll                      PASS      31.35 seconds
BluezMake                     PASS      1114.06 seconds
MakeCheck                     PASS      12.21 seconds
MakeDistcheck                 PASS      173.74 seconds
CheckValgrind                 PASS      279.47 seconds
CheckSmatch                   WARNING   410.45 seconds
bluezmakeextell               PASS      122.44 seconds
IncrementalBuild              PASS      4864.81 seconds
ScanBuild                     PASS      1312.92 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,v3,3/5] monitor: Print channel latency information with -a/--analyze
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#96: 
  10000 +-+----------------------------------------------------------------+

/github/workspace/src/src/13337398.patch total: 0 errors, 1 warnings, 255 lines checked

NOTE: For some of the reported defects, checkpatch may be able to
      mechanically convert to the typical style using --fix or --fix-inplace.

/github/workspace/src/src/13337398.patch has style problems, please review.

NOTE: Ignored message types: COMMIT_MESSAGE COMPLEX_MACRO CONST_STRUCT FILE_PATH_CHANGES MISSING_SIGN_OFF PREFER_PACKED SPDX_LICENSE_TAG SPLIT_STRING SSCANF_TO_KSTRTO

NOTE: If any of the errors are false positives, please report
      them to the maintainer, see CHECKPATCH in MAINTAINERS.


##############################
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:3602:52: warning: array of flexible structuresmonitor/bt.h:3590:40: warning: array of flexible structures


---
Regards,
Linux Bluetooth


  parent reply	other threads:[~2023-08-02  3:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-01 23:31 [BlueZ PATCH v3 1/5] monitor: Add TX frame number and speed estimation Luiz Augusto von Dentz
2023-08-01 23:31 ` [BlueZ PATCH v3 2/5] monitor/analyze: Use conn_pkt_tx on acl_pkt Luiz Augusto von Dentz
2023-08-01 23:31 ` [BlueZ PATCH v3 3/5] monitor: Print channel latency information with -a/--analyze Luiz Augusto von Dentz
2023-08-01 23:31 ` [BlueZ PATCH v3 4/5] monitor: Add connection tracking for SCO/ISO " Luiz Augusto von Dentz
2023-08-01 23:31 ` [BlueZ PATCH v3 5/5] monitor/analyze: Inline data to gnuplot Luiz Augusto von Dentz
2023-08-02  3:21 ` bluez.test.bot [this message]
2023-08-02 21:00 ` [BlueZ PATCH v3 1/5] monitor: Add TX frame number and speed estimation 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=64c9cba1.170a0220.f573e.95ab@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    /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.