From: David Lechner <david@lechnology.com>
To: linux-bluetooth@vger.kernel.org
Cc: David Lechner <david@lechnology.com>,
Miao-chen Chou <mcchou@chromium.org>,
Archie Pusaka <apusaka@chromium.org>,
Manish Mandlik <mmandlik@google.com>
Subject: [PATCH BlueZ] doc/advmon-api: Clarify Patterns property
Date: Mon, 10 May 2021 14:47:07 -0500 [thread overview]
Message-ID: <20210510194707.300130-1-david@lechnology.com> (raw)
The Patterns property description was not as clear as it could be. This
expands the text a bit, replaces the C enum value 0x01 with the D-Bus
property string value "or_patterns" and improves the grammar in a few
places.
---
Related question: How can we create an advertisement monitor with no filter?
Currently, "or_patterns" is the only Type and therefore a pattern is required.
doc/advertisement-monitor-api.txt | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/doc/advertisement-monitor-api.txt b/doc/advertisement-monitor-api.txt
index 8100717c0..9189f2cce 100644
--- a/doc/advertisement-monitor-api.txt
+++ b/doc/advertisement-monitor-api.txt
@@ -105,10 +105,11 @@ Properties string Type [read-only]
array{(uint8, uint8, array{byte})} Patterns [read-only, optional]
- If Type is set to 0x01, this must exist and has at least
- one entry in the array.
+ If the Type property is set to "or_patterns", then this
+ property must exist and have at least one entry in the
+ array.
- The structure of a pattern contains the following.
+ The structure of a pattern contains the following:
uint8 start_position
The index in an AD data field where the search
should start. The beginning of an AD data field
--
2.25.1
next reply other threads:[~2021-05-10 20:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 19:47 David Lechner [this message]
2021-05-10 20:39 ` [BlueZ] doc/advmon-api: Clarify Patterns property bluez.test.bot
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=20210510194707.300130-1-david@lechnology.com \
--to=david@lechnology.com \
--cc=apusaka@chromium.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mcchou@chromium.org \
--cc=mmandlik@google.com \
/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