From: Archie Pusaka <apusaka@google.com>
To: linux-bluetooth <linux-bluetooth@vger.kernel.org>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Marcel Holtmann <marcel@holtmann.org>
Cc: CrosBT Upstreaming <chromeos-bluetooth-upstreaming@chromium.org>,
Archie Pusaka <apusaka@chromium.org>
Subject: [Bluez PATCH] tools/hcitool: Fix the descriptions of leal* commands
Date: Fri, 24 Sep 2021 17:29:21 +0800 [thread overview]
Message-ID: <20210924172910.Bluez.1.I9b71a5f022d2b7197de347c7afa6005bd1d21b5b@changeid> (raw)
From: Archie Pusaka <apusaka@chromium.org>
The descriptions of leal* commands are copied from lewl* commands.
However they should use "accept list" instead.
---
tools/hcitool.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/tools/hcitool.c b/tools/hcitool.c
index b6f4a4e665..639ee6a511 100644
--- a/tools/hcitool.c
+++ b/tools/hcitool.c
@@ -3400,10 +3400,10 @@ static struct {
{ "clock", cmd_clock, "Read local or remote clock" },
{ "lescan", cmd_lescan, "Start LE scan" },
{ "leinfo", cmd_leinfo, "Get LE remote information" },
- { "lealadd", cmd_lealadd, "Add device to LE White List" },
- { "lealrm", cmd_lealrm, "Remove device from LE White List" },
- { "lealsz", cmd_lealsz, "Read size of LE White List" },
- { "lealclr", cmd_lealclr, "Clear LE White List" },
+ { "lealadd", cmd_lealadd, "Add device to LE Accept List" },
+ { "lealrm", cmd_lealrm, "Remove device from LE Accept List" },
+ { "lealsz", cmd_lealsz, "Read size of LE Accept List" },
+ { "lealclr", cmd_lealclr, "Clear LE Accept List" },
{ "lewladd", cmd_lealadd, "Deprecated. Use lealadd instead." },
{ "lewlrm", cmd_lealrm, "Deprecated. Use lealrm instead." },
{ "lewlsz", cmd_lealsz, "Deprecated. Use lealsz instead." },
--
2.33.0.685.g46640cef36-goog
next reply other threads:[~2021-09-24 9:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 9:29 Archie Pusaka [this message]
2021-10-21 20:31 ` [Bluez PATCH] tools/hcitool: Fix the descriptions of leal* commands 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=20210924172910.Bluez.1.I9b71a5f022d2b7197de347c7afa6005bd1d21b5b@changeid \
--to=apusaka@google.com \
--cc=apusaka@chromium.org \
--cc=chromeos-bluetooth-upstreaming@chromium.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.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).