From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,v3,1/3] shared/bap: Rework stream procedures
Date: Tue, 06 Feb 2024 16:29:00 -0800 (PST) [thread overview]
Message-ID: <65c2cecc.170a0220.c4977.0a5f@mx.google.com> (raw)
In-Reply-To: <20240206223513.2783330-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2782 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=823751
---Test result---
Test Summary:
CheckPatch PASS 1.50 seconds
GitLint FAIL 0.87 seconds
BuildEll PASS 24.31 seconds
BluezMake PASS 708.93 seconds
MakeCheck PASS 11.20 seconds
MakeDistcheck PASS 162.85 seconds
CheckValgrind PASS 226.06 seconds
CheckSmatch PASS 326.92 seconds
bluezmakeextell PASS 106.50 seconds
IncrementalBuild PASS 2009.42 seconds
ScanBuild WARNING 943.01 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[BlueZ,v3,3/3] shared/bap: Make bt_bap_ref_safe check if the instance is attached
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 (81>80): "[BlueZ,v3,3/3] shared/bap: Make bt_bap_ref_safe check if the instance is attached"
##############################
Test: ScanBuild - WARNING
Desc: Run Scan Build
Output:
src/shared/bap.c:1132:2: warning: Use of memory after it is freed
DBG(bap, "stream %p", stream);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/shared/bap.c:40:2: note: expanded from macro 'DBG'
bap_debug(_bap, "%s:%s() " fmt, __FILE__, __func__, ## arg)
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/shared/bap.c:1145:2: warning: Use of memory after it is freed
DBG(stream->bap, "stream %p", stream);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/shared/bap.c:40:2: note: expanded from macro 'DBG'
bap_debug(_bap, "%s:%s() " fmt, __FILE__, __func__, ## arg)
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/shared/bap.c:1240:33: warning: Use of memory after it is freed
for (entry = queue_get_entries(bap->state_cbs); entry;
^~~~~~~~~~~~~~
src/shared/bap.c:1698:3: warning: Use of memory after it is freed
stream_set_state(stream, BT_BAP_STREAM_STATE_CONFIG);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
4 warnings generated.
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2024-02-07 0:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 22:35 [PATCH BlueZ v3 1/3] shared/bap: Rework stream procedures Luiz Augusto von Dentz
2024-02-06 22:35 ` [PATCH BlueZ v3 2/3] shared/bap: Add .set_state to bt_bap_stream_ops Luiz Augusto von Dentz
2024-02-06 22:35 ` [PATCH BlueZ v3 3/3] shared/bap: Make bt_bap_ref_safe check if the instance is attached Luiz Augusto von Dentz
2024-02-07 0:29 ` bluez.test.bot [this message]
2024-02-08 18:50 ` [PATCH BlueZ v3 1/3] shared/bap: Rework stream procedures 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=65c2cecc.170a0220.c4977.0a5f@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).