From: Michael Sun <michaelfsun@google.com>
To: linux-bluetooth@vger.kernel.org
Cc: mcchou@chromium.org, chromeos-bluetooth-upstreaming@chromium.org,
luiz.von.dentz@intel.com, alainm@chromium.org,
Michael Sun <michaelfsun@google.com>
Subject: [bluez PATCH v3 0/3] Add new commands in btmgmt to support adv monitor
Date: Wed, 17 Jun 2020 00:55:33 -0700 [thread overview]
Message-ID: <20200617075536.98672-1-michaelfsun@google.com> (raw)
Hi linux-bluetooth,
This series of patches add support for new advertisement monitor mgmt
opcodes by introducing new btmgmt commands into a new submenu
'monitor'. The new commands are ‘features’, ‘add’, and ‘remove’. They
provide the ability for users to query supported advertisement
monitoring features and add/remove monitor filters through btmgmt
console.
Changes in v3:
- Fix build errors
Changes in v2:
- Move features command into submenu and fix build warnings
- Move remove command into submenu and fix build warnings
- Move add command into submenu and fix build warnings
Michael Sun (3):
btmgmt: Add "monitor" btmgmt submenu and command "features"
btmgmt: Add command "remove" into "monitor" btmgmt submenu
btmgmt: Add command "add" into "monitor" btmgmt submenu
tools/btmgmt.c | 302 +++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 302 insertions(+)
--
2.27.0.290.gba653c62da-goog
next reply other threads:[~2020-06-17 7:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 7:55 Michael Sun [this message]
2020-06-17 7:55 ` [bluez PATCH v3 1/3] btmgmt: Add "monitor" btmgmt submenu and command "features" Michael Sun
2020-06-17 7:55 ` [bluez PATCH v3 2/3] btmgmt: Add command "remove" into "monitor" btmgmt submenu Michael Sun
2020-06-17 8:08 ` [bluez,v3,2/3] " bluez.test.bot
2020-06-17 7:55 ` [bluez PATCH v3 3/3] btmgmt: Add command "add" " Michael Sun
2020-06-17 8:08 ` [bluez,v3,3/3] " bluez.test.bot
2020-06-17 15:01 ` [bluez PATCH v3 3/3] " Von Dentz, Luiz
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=20200617075536.98672-1-michaelfsun@google.com \
--to=michaelfsun@google.com \
--cc=alainm@chromium.org \
--cc=chromeos-bluetooth-upstreaming@chromium.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.von.dentz@intel.com \
--cc=mcchou@chromium.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.