From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, dmartinez@starry.com
Subject: RE: Optionally require security for notify/indicate
Date: Wed, 29 Sep 2021 11:39:03 -0700 (PDT) [thread overview]
Message-ID: <6154b2c7.1c69fb81.1c2a0.3333@mx.google.com> (raw)
In-Reply-To: <20210929180031.417090-2-dmartinez@starry.com>
[-- Attachment #1: Type: text/plain, Size: 2462 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=555169
---Test result---
Test Summary:
CheckPatch PASS 2.64 seconds
GitLint PASS 1.90 seconds
Prep - Setup ELL PASS 42.17 seconds
Build - Prep PASS 0.46 seconds
Build - Configure PASS 7.81 seconds
Build - Make FAIL 149.53 seconds
Make Check FAIL 1.57 seconds
Make Distcheck PASS 213.11 seconds
Build w/ext ELL - Configure PASS 7.91 seconds
Build w/ext ELL - Make FAIL 141.46 seconds
Details
##############################
Test: Build - Make - FAIL
Desc: Build the BlueZ source tree
Output:
src/gatt-database.c: In function ‘service_add_ccc’:
src/gatt-database.c:1060:2: error: ISO C90 forbids mixed declarations and code [-Werror=declaration-after-statement]
1060 | uint32_t permissions = BT_ATT_PERM_READ | BT_ATT_PERM_WRITE;
| ^~~~~~~~
cc1: all warnings being treated as errors
make[1]: *** [Makefile:9212: src/bluetoothd-gatt-database.o] Error 1
make: *** [Makefile:4151: all] Error 2
##############################
Test: Make Check - FAIL
Desc: Run 'make check'
Output:
src/gatt-database.c: In function ‘service_add_ccc’:
src/gatt-database.c:1060:2: error: ISO C90 forbids mixed declarations and code [-Werror=declaration-after-statement]
1060 | uint32_t permissions = BT_ATT_PERM_READ | BT_ATT_PERM_WRITE;
| ^~~~~~~~
cc1: all warnings being treated as errors
make[1]: *** [Makefile:9212: src/bluetoothd-gatt-database.o] Error 1
make: *** [Makefile:10443: check] Error 2
##############################
Test: Build w/ext ELL - Make - FAIL
Desc: Build BlueZ source with '--enable-external-ell' configuration
Output:
src/gatt-database.c: In function ‘service_add_ccc’:
src/gatt-database.c:1060:2: error: ISO C90 forbids mixed declarations and code [-Werror=declaration-after-statement]
1060 | uint32_t permissions = BT_ATT_PERM_READ | BT_ATT_PERM_WRITE;
| ^~~~~~~~
cc1: all warnings being treated as errors
make[1]: *** [Makefile:9212: src/bluetoothd-gatt-database.o] Error 1
make: *** [Makefile:4151: all] Error 2
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2021-09-29 18:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 18:00 [PATCH BlueZ v2 0/2] Optionally require security for notify/indicate Dagan Martinez
2021-09-29 18:00 ` [PATCH BlueZ v2 1/2] gatt: allow GATT server to dicate CCC permissions Dagan Martinez
2021-09-29 18:39 ` bluez.test.bot [this message]
2021-09-29 18:00 ` [PATCH BlueZ v2 2/2] doc/gatt-api: Add 'X-asynchronous` permissions Dagan Martinez
-- strict thread matches above, loose matches on Subject: below --
2021-09-29 16:16 [PATCH BlueZ 1/2] gatt: allow GATT server to dicate CCC permissions Dagan Martinez
2021-09-29 16:49 ` Optionally require security for notify/indicate 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=6154b2c7.1c69fb81.1c2a0.3333@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=dmartinez@starry.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.