From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, simon.mikuda@streamunlimited.com
Subject: RE: Report proper error on connect
Date: Sun, 06 Aug 2023 02:51:47 -0700 (PDT) [thread overview]
Message-ID: <64cf6d33.050a0220.3ed28.0362@mx.google.com> (raw)
In-Reply-To: <20230806080109.1639693-2-simon.mikuda@streamunlimited.com>
[-- Attachment #1: Type: text/plain, Size: 1206 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=773409
---Test result---
Test Summary:
CheckPatch PASS 0.92 seconds
GitLint PASS 0.63 seconds
BuildEll PASS 32.96 seconds
BluezMake PASS 1188.84 seconds
MakeCheck PASS 13.56 seconds
MakeDistcheck PASS 193.65 seconds
CheckValgrind PASS 317.85 seconds
CheckSmatch PASS 443.22 seconds
bluezmakeextell PASS 132.21 seconds
IncrementalBuild PASS 2073.05 seconds
ScanBuild WARNING 1396.94 seconds
Details
##############################
Test: ScanBuild - WARNING
Desc: Run Scan Build
Output:
profiles/audio/a2dp.c:352:8: warning: Use of memory after it is freed
if (!cb->resume_cb)
^~~~~~~~~~~~~
1 warning generated.
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-08-06 9:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-06 8:01 [PATCH BlueZ 0/2] Report proper error on connect Simon Mikuda
2023-08-06 8:01 ` [PATCH BlueZ 1/2] error: Add "Invalid exchange" mapping Simon Mikuda
2023-08-06 9:51 ` bluez.test.bot [this message]
2023-08-06 8:01 ` [PATCH BlueZ 2/2] a2dp: Expose "Key missing" error Simon Mikuda
2023-08-07 23:20 ` [PATCH BlueZ 0/2] Report proper error on connect 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=64cf6d33.050a0220.3ed28.0362@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=simon.mikuda@streamunlimited.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