From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, mcchou@chromium.org
Subject: RE: [BlueZ,v4,1/8] adv_monitor: Implement RSSI Filter logic for background scanning
Date: Thu, 17 Sep 2020 00:32:23 -0700 (PDT) [thread overview]
Message-ID: <5f631107.1c69fb81.7353d.f98c@mx.google.com> (raw)
In-Reply-To: <20200917001020.BlueZ.v4.1.I2830b9c1212a64b062201ed9f2b71294f50ad22d@changeid>
[-- Attachment #1: Type: text/plain, Size: 1651 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.
While we are preparing for reviewing the patches, we found the following
issue/warning.
Test Result:
checkbuild Failed
Outputs:
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
src/adv_monitor.c: In function ‘adv_monitor_removed_callback’:
src/adv_monitor.c:1030:30: error: ‘manager’ undeclared (first use in this function)
1030 | const uint16_t adapter_id = manager->adapter_id;
| ^~~~~~~
src/adv_monitor.c:1030:30: note: each undeclared identifier is reported only once for each function it appears in
src/adv_monitor.c:1041:51: error: passing argument 3 of ‘queue_foreach’ discards ‘const’ qualifier from pointer target type [-Werror=discarded-qualifiers]
1041 | queue_foreach(manager->apps, app_remove_monitor, ev);
| ^~
In file included from src/adv_monitor.c:42:
./src/shared/queue.h:48:14: note: expected ‘void *’ but argument is of type ‘const struct mgmt_ev_adv_monitor_removed *’
48 | void *user_data);
| ~~~~~~^~~~~~~~~
cc1: all warnings being treated as errors
make[1]: *** [Makefile:6863: src/adv_monitor.o] Error 1
make: *** [Makefile:4056: all] Error 2
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2020-09-17 7:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 7:10 [BlueZ PATCH v4 1/8] adv_monitor: Implement RSSI Filter logic for background scanning Miao-chen Chou
2020-09-17 7:10 ` [BlueZ PATCH v4 2/8] adv_monitor: Implement unit tests for RSSI Filter Miao-chen Chou
2020-09-17 7:29 ` [BlueZ,v4,2/8] " bluez.test.bot
2020-09-17 7:10 ` [BlueZ PATCH v4 3/8] adv_monitor: Implement Adv matching based on stored monitors Miao-chen Chou
2020-09-17 7:10 ` [BlueZ PATCH v4 4/8] adv_monitor: Implement unit tests for content filter Miao-chen Chou
2020-09-17 7:10 ` [BlueZ PATCH v4 5/8] adapter: Clear all Adv monitors upon bring-up Miao-chen Chou
2020-09-17 7:10 ` [BlueZ PATCH v4 6/8] adv_monitor: Implement Add Adv Patterns Monitor cmd handler Miao-chen Chou
2020-09-17 7:10 ` [BlueZ PATCH v4 7/8] adv_monitor: Fix return type of RegisterMonitor() method Miao-chen Chou
2020-09-17 7:10 ` [BlueZ PATCH v4 8/8] adv_monitor: Issue Remove Adv Monitor mgmt call Miao-chen Chou
2020-09-17 7:32 ` bluez.test.bot [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-09-17 21:25 [BlueZ PATCH v4 1/8] adv_monitor: Implement RSSI Filter logic for background scanning Miao-chen Chou
2020-09-17 21:51 ` [BlueZ,v4,1/8] " 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=5f631107.1c69fb81.7353d.f98c@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mcchou@chromium.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;
as well as URLs for NNTP newsgroup(s).