From: Szymon Janc <szymon.janc@codecoup.pl>
To: Grzegorz Kolodziejczyk <grzegorz.kolodziejczyk@codecoup.pl>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 1/4] tools/btpclient: Fix ad property manufacturer data name
Date: Tue, 13 Feb 2018 09:15:20 +0100 [thread overview]
Message-ID: <2532752.SEh91lMQ4G@ix> (raw)
In-Reply-To: <20180212160102.31451-1-grzegorz.kolodziejczyk@codecoup.pl>
Hi Grzegorz,
On Monday, 12 February 2018 17:00:59 CET Grzegorz Kolodziejczyk wrote:
> This patch fixes wrong naming of advertising instance data property.
> ---
> tools/btpclient.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/btpclient.c b/tools/btpclient.c
> index 097732eb8..61bde820e 100644
> --- a/tools/btpclient.c
> +++ b/tools/btpclient.c
> @@ -971,7 +971,7 @@ static void setup_ad_interface(struct l_dbus_interface
> *interface) ad_serviceuuids_getter, NULL);
> l_dbus_interface_property(interface, "ServiceData", 0, "a{sv}",
> ad_servicedata_getter, NULL);
> - l_dbus_interface_property(interface, "ManufacturerServiceData", 0,
> + l_dbus_interface_property(interface, "ManufacturerData", 0,
> "a{qv}", ad_manufacturerdata_getter,
> NULL);
> l_dbus_interface_property(interface, "Includes", 0, "as",
Patches 1 and 2 are now applied, thanks.
--
pozdrawiam
Szymon Janc
prev parent reply other threads:[~2018-02-13 8:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 16:00 [PATCH BlueZ 1/4] tools/btpclient: Fix ad property manufacturer data name Grzegorz Kolodziejczyk
2018-02-12 16:01 ` [PATCH BlueZ 2/4] shared/btp: Change struct member order for device found as in btp Grzegorz Kolodziejczyk
2018-02-12 16:01 ` [PATCH BlueZ 3/4] tools/btpclient: Add passkey confirm ev and passkey confirm rsp cmd Grzegorz Kolodziejczyk
2018-02-12 16:01 ` [PATCH BlueZ 4/4] tools/btpclient: Check if dev is connected in device found ev routine Grzegorz Kolodziejczyk
2018-02-13 8:15 ` 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=2532752.SEh91lMQ4G@ix \
--to=szymon.janc@codecoup.pl \
--cc=grzegorz.kolodziejczyk@codecoup.pl \
--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