From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, abhay.maheshbhai.maheta@intel.com
Subject: RE: To add support for Metadata, CID, VID
Date: Sat, 29 Oct 2022 10:42:03 -0700 (PDT) [thread overview]
Message-ID: <635d65eb.050a0220.79231.22a9@mx.google.com> (raw)
In-Reply-To: <20221029170408.175533-2-abhay.maheshbhai.maheta@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2056 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=690159
---Test result---
Test Summary:
CheckPatch PASS 5.60 seconds
GitLint PASS 3.64 seconds
Prep - Setup ELL PASS 26.71 seconds
Build - Prep PASS 0.68 seconds
Build - Configure PASS 8.32 seconds
Build - Make PASS 749.65 seconds
Make Check PASS 11.86 seconds
Make Check w/Valgrind PASS 292.31 seconds
Make Distcheck PASS 240.14 seconds
Build w/ext ELL - Configure PASS 8.38 seconds
Build w/ext ELL - Make PASS 85.77 seconds
Incremental Build w/ patches PASS 503.62 seconds
Scan Build WARNING 547.38 seconds
Details
##############################
Test: Scan Build - WARNING
Desc: Run Scan Build with patches
Output:
*****************************************************************************
The bugs reported by the scan-build may or may not be caused by your patches.
Please check the list and fix the bugs if they are caused by your patch.
*****************************************************************************
client/player.c:1770:25: warning: Dereference of null pointer
iov_append(&cfg->caps, preset->data.iov_base, preset->data.iov_len);
^~~~~~~~~~~~~~~~~~~~~
1 warning generated.
profiles/audio/media.c:1159:3: warning: Potential leak of memory pointed to by 'metadata'
error("Could not allocate name for pac %s:%s",
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
./src/log.h:62:2: note: expanded from macro 'error'
btd_error(0xffff, "%s:%s() " fmt, __FILE__, __func__, ## arg)
^~~~~~~~~
1 warning generated.
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-10-29 17:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-29 17:04 [PATCH BlueZ 0/5] To add support for Metadata, CID, VID Abhay Maheta
2022-10-29 17:04 ` [PATCH BlueZ 1/5] shared/bap: Fix handling for Company ID and Vendor Codec ID Abhay Maheta
2022-10-29 17:42 ` bluez.test.bot [this message]
2022-10-31 20:48 ` Luiz Augusto von Dentz
2022-10-29 17:04 ` [PATCH BlueZ 2/5] shared/bap: Add support to set stream metadata Abhay Maheta
2022-10-31 21:13 ` Luiz Augusto von Dentz
2022-10-29 17:04 ` [PATCH BlueZ 3/5] profiles: Add Support for Metadata, CID and VID Abhay Maheta
2022-10-29 17:04 ` [PATCH BlueZ 4/5] media-api: Add CompanyID, VendorCodecID, Metadata Abhay Maheta
2022-10-31 20:57 ` Luiz Augusto von Dentz
2022-10-29 17:04 ` [PATCH BlueZ 5/5] client/player: Add support for Metadata, CID, VID Abhay Maheta
2022-10-31 21:29 ` Luiz Augusto von Dentz
-- strict thread matches above, loose matches on Subject: below --
2022-12-29 12:28 [PATCH BlueZ v2 1/6] shared/bap: Fix handling for Company ID and Vendor Codec ID Abhay Maheta
2022-12-29 14:17 ` To add support for Metadata, CID, VID bluez.test.bot
2022-12-29 15:52 [PATCH BlueZ v3 1/6] shared/bap: Fix handling for Company ID and Vendor Codec ID Abhay Maheta
2022-12-29 17:31 ` To add support for Metadata, CID, VID 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=635d65eb.050a0220.79231.22a9@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=abhay.maheshbhai.maheta@intel.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.