From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, nitin.jadhav@nxp.com
Subject: RE: Fixed the crash observed with VOCS when pairing with LE Audio TWS earbuds
Date: Mon, 24 Jul 2023 03:23:19 -0700 (PDT) [thread overview]
Message-ID: <64be5117.a70a0220.58afd.c6da@mx.google.com> (raw)
In-Reply-To: <20230724085530.5555-2-nitin.jadhav@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 2135 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=768787
---Test result---
Test Summary:
CheckPatch PASS 0.40 seconds
GitLint FAIL 0.64 seconds
BuildEll PASS 32.68 seconds
BluezMake PASS 990.43 seconds
MakeCheck PASS 13.04 seconds
MakeDistcheck PASS 185.50 seconds
CheckValgrind PASS 300.84 seconds
CheckSmatch PASS 394.85 seconds
bluezmakeextell PASS 121.85 seconds
IncrementalBuild PASS 809.02 seconds
ScanBuild WARNING 1239.51 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[BlueZ,v1,1/1] shared/vcp: Fixed the crash observed with VOCS when pairing with LE Audio TWS earbuds
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
1: T1 Title exceeds max length (100>80): "[BlueZ,v1,1/1] shared/vcp: Fixed the crash observed with VOCS when pairing with LE Audio TWS earbuds"
##############################
Test: ScanBuild - WARNING
Desc: Run Scan Build
Output:
src/shared/vcp.c:1424:3: warning: Potential leak of memory pointed to by 'vocs_ao_dec_r'
DBG(vcp, "Unable to read VOCS Audio Descriptor: error 0x%02x",
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/shared/vcp.c:31:2: note: expanded from macro 'DBG'
vcp_debug(_vcp, "%s:%s() " fmt, __FILE__, __func__, ## arg)
^~~~~~~~~
1 warning generated.
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2023-07-24 10:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 8:55 [PATCH BlueZ v1 0/1] Fixed the crash observed with VOCS when pairing with LE Audio TWS earbuds Nitin Jadhav
2023-07-24 8:55 ` [PATCH BlueZ v1 1/1] shared/vcp: " Nitin Jadhav
2023-07-24 10:23 ` bluez.test.bot [this message]
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=64be5117.a70a0220.58afd.c6da@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=nitin.jadhav@nxp.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.