From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, alainm@chromium.org
Subject: RE: [Bluez] gatt: Support DeviceInfo Service when vid/pid is specified
Date: Fri, 17 Jul 2020 06:49:47 -0700 (PDT) [thread overview]
Message-ID: <5f11ac7b.1c69fb81.2b25.91a8@mx.google.com> (raw)
In-Reply-To: <20200717134251.3148686-1-alainm@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 1568 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')
In file included from peripheral/gatt.c:44:
./src/hcid.h:53:2: error: unknown type name ‘gboolean’
53 | gboolean pairable;
| ^~~~~~~~
./src/hcid.h:99:2: error: unknown type name ‘gboolean’
99 | gboolean reverse_discovery;
| ^~~~~~~~
./src/hcid.h:100:2: error: unknown type name ‘gboolean’
100 | gboolean name_resolv;
| ^~~~~~~~
./src/hcid.h:101:2: error: unknown type name ‘gboolean’
101 | gboolean debug_keys;
| ^~~~~~~~
./src/hcid.h:102:2: error: unknown type name ‘gboolean’
102 | gboolean fast_conn;
| ^~~~~~~~
./src/hcid.h:122:1: error: unknown type name ‘gboolean’
122 | gboolean plugin_init(const char *enable, const char *disable);
| ^~~~~~~~
./src/hcid.h:128:1: error: unknown type name ‘GKeyFile’
128 | GKeyFile *btd_get_main_conf(void);
| ^~~~~~~~
make[1]: *** [Makefile:6791: peripheral/gatt.o] Error 1
make: *** [Makefile:4010: all] Error 2
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2020-07-17 13:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 13:42 [Bluez PATCH] gatt: Support DeviceInfo Service when vid/pid is specified Alain Michaud
2020-07-17 13:49 ` bluez.test.bot [this message]
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=5f11ac7b.1c69fb81.2b25.91a8@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=alainm@chromium.org \
--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;
as well as URLs for NNTP newsgroup(s).