From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, kiran.k@intel.com
Subject: RE: [v1,1/5] avdtp: Add a flag in struct avdtp to control a2dp offload
Date: Mon, 15 Nov 2021 01:55:33 -0800 (PST) [thread overview]
Message-ID: <61922e95.1c69fb81.3ebbc.88e4@mx.google.com> (raw)
In-Reply-To: <20211115094108.24331-1-kiran.k@intel.com>
[-- Attachment #1: Type: text/plain, Size: 3365 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=580019
---Test result---
Test Summary:
CheckPatch PASS 7.21 seconds
GitLint PASS 4.81 seconds
Prep - Setup ELL PASS 42.19 seconds
Build - Prep PASS 0.53 seconds
Build - Configure PASS 7.91 seconds
Build - Make FAIL 138.55 seconds
Make Check FAIL 1.60 seconds
Make Distcheck PASS 214.63 seconds
Build w/ext ELL - Configure PASS 8.04 seconds
Build w/ext ELL - Make FAIL 128.87 seconds
Details
##############################
Test: Build - Make - FAIL
Desc: Build the BlueZ source tree
Output:
profiles/audio/avdtp.c: In function ‘avdtp_connect_cb’:
profiles/audio/avdtp.c:2374:6: error: ‘cap’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
2374 | if (setsockopt(sock, SOL_BLUETOOTH, BT_MSFT_OPEN, cap,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2375 | sizeof(*cap) + cap->length))
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~
profiles/audio/avdtp.c:2358:35: note: ‘cap’ was declared here
2358 | struct avdtp_service_capability *cap;
| ^~~
cc1: all warnings being treated as errors
make[1]: *** [Makefile:8640: profiles/audio/bluetoothd-avdtp.o] Error 1
make: *** [Makefile:4175: all] Error 2
##############################
Test: Make Check - FAIL
Desc: Run 'make check'
Output:
profiles/audio/avdtp.c: In function ‘avdtp_connect_cb’:
profiles/audio/avdtp.c:2374:6: error: ‘cap’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
2374 | if (setsockopt(sock, SOL_BLUETOOTH, BT_MSFT_OPEN, cap,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2375 | sizeof(*cap) + cap->length))
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~
profiles/audio/avdtp.c:2358:35: note: ‘cap’ was declared here
2358 | struct avdtp_service_capability *cap;
| ^~~
cc1: all warnings being treated as errors
make[1]: *** [Makefile:8640: profiles/audio/bluetoothd-avdtp.o] Error 1
make: *** [Makefile:10501: check] Error 2
##############################
Test: Build w/ext ELL - Make - FAIL
Desc: Build BlueZ source with '--enable-external-ell' configuration
Output:
profiles/audio/avdtp.c: In function ‘avdtp_connect_cb’:
profiles/audio/avdtp.c:2374:6: error: ‘cap’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
2374 | if (setsockopt(sock, SOL_BLUETOOTH, BT_MSFT_OPEN, cap,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2375 | sizeof(*cap) + cap->length))
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~
profiles/audio/avdtp.c:2358:35: note: ‘cap’ was declared here
2358 | struct avdtp_service_capability *cap;
| ^~~
cc1: all warnings being treated as errors
make[1]: *** [Makefile:8640: profiles/audio/bluetoothd-avdtp.o] Error 1
make: *** [Makefile:4175: all] Error 2
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2021-11-15 9:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 9:41 [PATCH v1 1/5] avdtp: Add a flag in struct avdtp to control a2dp offload Kiran K
2021-11-15 9:41 ` [PATCH v1 2/5] avdtp: Add support for offload msft open command Kiran K
2021-11-15 9:41 ` [PATCH v1 3/5] avdtp: Add support for offload msft start command Kiran K
2021-11-15 9:41 ` [PATCH v1 4/5] avdtp: Add support for offload msft suspend command Kiran K
2021-11-15 9:41 ` [PATCH v1 5/5] avdtp: Add support for offload msft close command Kiran K
2021-11-15 9:55 ` bluez.test.bot [this message]
2021-11-15 19:42 ` [PATCH v1 1/5] avdtp: Add a flag in struct avdtp to control a2dp offload Luiz Augusto von Dentz
2021-11-15 19:44 ` Luiz Augusto von Dentz
2021-11-19 8:12 ` K, Kiran
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=61922e95.1c69fb81.3ebbc.88e4@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=kiran.k@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox