From: Szymon Janc <szymon.janc@tieto.com>
To: Grzegorz Kolodziejczyk <grzegorz.kolodziejczyk@tieto.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v2 1/6] android/tester: Make client2 app uuid value name consistent
Date: Mon, 06 Oct 2014 13:11:59 +0200 [thread overview]
Message-ID: <3730533.q5ECsSFLWj@uw000953> (raw)
In-Reply-To: <1412325892-25013-1-git-send-email-grzegorz.kolodziejczyk@tieto.com>
Hi Grzegorz,
On Friday 03 of October 2014 10:44:47 Grzegorz Kolodziejczyk wrote:
> Application uudis for tester should be name unified and consistent.
> ---
> android/tester-gatt.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/android/tester-gatt.c b/android/tester-gatt.c
> index 4c9eba5..4326749 100644
> --- a/android/tester-gatt.c
> +++ b/android/tester-gatt.c
> @@ -41,6 +41,11 @@ static bt_uuid_t app1_uuid = {
> 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01 },
> };
>
> +static bt_uuid_t app2_uuid = {
> + .uu = { 0x02, 0x02, 0x02, 0x02, 0x02, 0x02, 0x02, 0x02, 0x02,
> + 0x02, 0x02, 0x02, 0x02, 0x02, 0x02, 0x02 },
> +};
> +
> struct gatt_connect_data {
> const int app_id;
> const int conn_id;
> @@ -101,11 +106,6 @@ struct notif_data {
> btgatt_gatt_id_t *charac;
> };
>
> -static bt_uuid_t client2_app_uuid = {
> - .uu = { 0x02, 0x02, 0x02, 0x02, 0x02, 0x02, 0x02, 0x02, 0x02,
> - 0x02, 0x02, 0x02, 0x02, 0x02, 0x02, 0x02 },
> -};
> -
> static bt_bdaddr_t emu_remote_bdaddr_val = {
> .address = { 0x00, 0xaa, 0x01, 0x01, 0x00, 0x00 },
> };
> @@ -1263,7 +1263,7 @@ static struct test_case test_cases[] = {
> ACTION_SUCCESS(emu_set_connect_cb_action, gatt_conn_cb),
> ACTION_SUCCESS(gatt_client_register_action, &app1_uuid),
> CALLBACK_STATUS(CB_GATTC_REGISTER_CLIENT, BT_STATUS_SUCCESS),
> - ACTION_SUCCESS(gatt_client_register_action, &client2_app_uuid),
> + ACTION_SUCCESS(gatt_client_register_action, &app2_uuid),
> CALLBACK_STATUS(CB_GATTC_REGISTER_CLIENT, BT_STATUS_SUCCESS),
> ACTION_SUCCESS(gatt_client_start_scan_action,
> INT_TO_PTR(APP1_ID)),
>
All patches applied, thanks.
--
Best regards,
Szymon Janc
prev parent reply other threads:[~2014-10-06 11:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-03 8:44 [PATCH v2 1/6] android/tester: Make client2 app uuid value name consistent Grzegorz Kolodziejczyk
2014-10-03 8:44 ` [PATCH v2 2/6] android/tester: Fix debug callback logs Grzegorz Kolodziejczyk
2014-10-03 8:44 ` [PATCH v2 3/6] android/tester: Change GATT client connection test cases to LE connect Grzegorz Kolodziejczyk
2014-10-03 8:44 ` [PATCH v2 4/6] android/tester: Add GATT server connect successful test case Grzegorz Kolodziejczyk
2014-10-03 8:44 ` [PATCH v2 5/6] android/tester: Add GATT server disconnect " Grzegorz Kolodziejczyk
2014-10-03 8:44 ` [PATCH v2 6/6] android/tester: Add GATT server multiple connect succesful " Grzegorz Kolodziejczyk
2014-10-06 11:11 ` Szymon Janc [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=3730533.q5ECsSFLWj@uw000953 \
--to=szymon.janc@tieto.com \
--cc=grzegorz.kolodziejczyk@tieto.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