From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, howardchung@google.com
Subject: RE: Fix descriptor display issue in btmon
Date: Wed, 03 Apr 2024 05:59:40 -0700 (PDT) [thread overview]
Message-ID: <660d52bc.050a0220.ceaf5.058e@mx.google.com> (raw)
In-Reply-To: <20240403190511.Bluez.1.I0e799d0a6494565e232db4c86a8979cf898b1840@changeid>
[-- Attachment #1: Type: text/plain, Size: 1262 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=841052
---Test result---
Test Summary:
CheckPatch PASS 1.11 seconds
GitLint PASS 0.77 seconds
BuildEll PASS 24.08 seconds
BluezMake PASS 1626.86 seconds
MakeCheck PASS 12.97 seconds
MakeDistcheck PASS 174.35 seconds
CheckValgrind PASS 244.01 seconds
CheckSmatch WARNING 346.65 seconds
bluezmakeextell PASS 117.47 seconds
IncrementalBuild PASS 2928.57 seconds
ScanBuild PASS 965.46 seconds
Details
##############################
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.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:[~2024-04-03 12:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 11:05 [Bluez PATCH 0/2] Fix descriptor display issue in btmon Howard Chung
2024-04-03 11:05 ` [Bluez PATCH 1/2] shared/gatt: Rename some gatt insert functions to append Howard Chung
2024-04-03 12:59 ` bluez.test.bot [this message]
2024-04-03 14:29 ` Luiz Augusto von Dentz
2024-04-03 11:05 ` [Bluez PATCH 2/2] shared/gatt: Add descriptor insert function Howard Chung
2024-04-03 14:36 ` Luiz Augusto von Dentz
2024-04-08 12:22 ` Yun-hao Chung
2024-04-08 14:03 ` Luiz Augusto von Dentz
2024-04-08 16:12 ` Luiz Augusto von Dentz
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=660d52bc.050a0220.ceaf5.058e@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=howardchung@google.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.