From: puthik@chromium.org
To: linux-bluetooth@vger.kernel.org
Cc: Puthikorn Voravootivat <puthik@chromium.org>
Subject: [PATCH v2 0/2] Expose AdvertisingDataFlags in Device API
Date: Tue, 18 Oct 2016 12:10:58 -0700 [thread overview]
Message-ID: <1476817861-24158-2-git-send-email-puthik@chromium.org> (raw)
In-Reply-To: <1476817861-24158-1-git-send-email-puthik@chromium.org>
From: Puthikorn Voravootivat <puthik@chromium.org>
The following patches expose AdvertisingFlags in Device API.
This is need by Android app on ChromeOS as Android normally
should get Advertising data flag from Bluetooth adapter.
v2:
Address Marcel's review to make it more future proof by making it array{byte}.
device->flags is still a uint8 because 1) We don't need it to be bigger now.
and 2) We can easily changed it to bigger type when needed without affecting
the DBus Device API.
Puthikorn Voravootivat (2):
doc/device-api: Add AdvertisingFlags
core: Add implementation of AdvertisingFlags
doc/device-api.txt | 4 ++++
src/adapter.c | 2 ++
src/device.c | 36 ++++++++++++++++++++++++++++++++++++
src/device.h | 1 +
4 files changed, 43 insertions(+)
--
2.8.0.rc3.226.g39d4020
next prev parent reply other threads:[~2016-10-18 19:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 19:10 [PATCH v2 0/2] Expose AdvertisingDataFlags in Device API puthik
2016-10-18 19:10 ` puthik [this message]
2016-10-18 19:10 ` [PATCH v2 1/2] doc/device-api: Add AdvertisingFlags puthik
2016-10-19 7:19 ` Luiz Augusto von Dentz
2016-10-19 16:15 ` Szymon Janc
2016-10-19 16:21 ` Luiz Augusto von Dentz
2016-10-19 17:15 ` Johan Hedberg
2016-10-20 1:54 ` Puthikorn Voravootivat
2016-10-18 19:11 ` [PATCH v2 2/2] core: Add implementation of AdvertisingFlags puthik
2016-10-19 7:23 ` Luiz Augusto von Dentz
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=1476817861-24158-2-git-send-email-puthik@chromium.org \
--to=puthik@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).