From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, apusaka@google.com
Subject: RE: [Bluez,v1] tools/l2cap-tester: Add test for waiting disconnection response
Date: Thu, 30 Apr 2020 00:07:53 -0700 (PDT) [thread overview]
Message-ID: <5eaa7949.1c69fb81.28ac0.7f1e@mx.google.com> (raw)
In-Reply-To: <20200430145105.Bluez.v1.1.I86c1e0e8933d92d8d76dcd95036bf325cfaeced0@changeid>
[-- Attachment #1: Type: text/plain, Size: 1306 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
Patch Series:
[Bluez,v1] tools/l2cap-tester: Add test for waiting disconnection response
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')
android/tester-main.c: In function ‘emu_add_l2cap_server_action’:
android/tester-main.c:2869:2: error: too few arguments to function ‘bthost_add_l2cap_server’
2869 | bthost_add_l2cap_server(bthost, l2cap_data->psm, l2cap_data->func,
| ^~~~~~~~~~~~~~~~~~~~~~~
In file included from android/tester-main.c:33:
./emulator/bthost.h:105:6: note: declared here
105 | void bthost_add_l2cap_server(struct bthost *bthost, uint16_t psm,
| ^~~~~~~~~~~~~~~~~~~~~~~
make[1]: *** [Makefile:7165: android/android_tester-tester-main.o] Error 1
make: *** [Makefile:4010: all] Error 2
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2020-04-30 7:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 6:51 [Bluez PATCH v1] tools/l2cap-tester: Add test for waiting disconnection response Archie Pusaka
2020-04-30 6:56 ` Archie Pusaka
2020-04-30 7:07 ` bluez.test.bot [this message]
2020-04-30 17:22 ` Luiz Augusto von Dentz
2020-05-05 4:37 ` Archie Pusaka
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=5eaa7949.1c69fb81.28ac0.7f1e@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=apusaka@google.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.