From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, silviu.barbulescu@nxp.com
Subject: RE: Add support for multiple BISes on the bcast source
Date: Fri, 23 Feb 2024 10:51:45 -0800 (PST) [thread overview]
Message-ID: <65d8e941.050a0220.4a056.95fc@mx.google.com> (raw)
In-Reply-To: <20240223164813.66484-2-silviu.barbulescu@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 1756 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=829188
---Test result---
Test Summary:
CheckPatch PASS 2.21 seconds
GitLint PASS 1.39 seconds
BuildEll PASS 24.08 seconds
BluezMake PASS 730.41 seconds
MakeCheck PASS 11.71 seconds
MakeDistcheck PASS 163.60 seconds
CheckValgrind PASS 226.46 seconds
CheckSmatch PASS 330.87 seconds
bluezmakeextell PASS 107.61 seconds
IncrementalBuild PASS 3404.27 seconds
ScanBuild WARNING 946.94 seconds
Details
##############################
Test: ScanBuild - WARNING
Desc: Run Scan Build
Output:
src/shared/bap.c:1147: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:1281:8: warning: Use of memory after it is freed
bap = bt_bap_ref_safe(bap);
^~~~~~~~~~~~~~~~~~~~
src/shared/bap.c:1699:3: warning: Use of memory after it is freed
stream_set_state(stream, BT_BAP_STREAM_STATE_CONFIG);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3 warnings generated.
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2024-02-23 18:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 16:48 [PATCH BlueZ v4 0/5] Add support for multiple BISes on the bcast source Silviu Florian Barbulescu
2024-02-23 16:48 ` [PATCH BlueZ v4 1/5] shared/bap: Fix endpoint dir for " Silviu Florian Barbulescu
2024-02-23 18:51 ` bluez.test.bot [this message]
2024-02-23 16:48 ` [PATCH BlueZ v4 2/5] shared/bap: Add state in stream struct for " Silviu Florian Barbulescu
2024-02-23 16:48 ` [PATCH BlueZ v4 3/5] shared/bap: Add support to create a stream for bcast src Silviu Florian Barbulescu
2024-02-23 16:48 ` [PATCH BlueZ v4 4/5] bap: Add a callback to create a new stream Silviu Florian Barbulescu
2024-02-23 16:48 ` [PATCH BlueZ v4 5/5] bap: Set generated BASE on all setups from the same BIG Silviu Florian Barbulescu
2024-02-27 14:30 ` [PATCH BlueZ v4 0/5] Add support for multiple BISes on the bcast source patchwork-bot+bluetooth
-- strict thread matches above, loose matches on Subject: below --
2024-02-15 21:23 [PATCH BlueZ v3 1/7] bap: Remove set lpac user data at bcast ep register Silviu Florian Barbulescu
2024-02-15 23:49 ` Add support for multiple BISes on the bcast source bluez.test.bot
2024-02-12 15:32 [PATCH BlueZ v2 1/7] bap: Remove set lpac user data at bcast ep register Silviu Florian Barbulescu
2024-02-12 17:39 ` Add support for multiple BISes on the bcast source bluez.test.bot
2024-02-01 15:28 [PATCH BlueZ 1/7] bap: Remove set lpac user data at bcast ep register Silviu Florian Barbulescu
2024-02-01 17:37 ` Add support for multiple BISes on the bcast source 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=65d8e941.050a0220.4a056.95fc@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=silviu.barbulescu@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 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).