From: David Nicolson <david.nicolson@gmail.com>
To: linux-bluetooth@vger.kernel.org
Cc: Dave Nicolson <david.nicolson@gmail.com>
Subject: [PATCH BlueZ] gatttool: Use consistent spacing before brackets
Date: Sun, 12 Feb 2023 18:24:02 +0100 [thread overview]
Message-ID: <20230212172402.19018-1-david.nicolson@gmail.com> (raw)
From: Dave Nicolson <david.nicolson@gmail.com>
---
attrib/gatttool.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/attrib/gatttool.c b/attrib/gatttool.c
index 6a0ddfaad..2d03875b0 100644
--- a/attrib/gatttool.c
+++ b/attrib/gatttool.c
@@ -456,17 +456,17 @@ static gboolean parse_uuid(const char *key, const char *value,
static GOptionEntry primary_char_options[] = {
{ "start", 's' , 0, G_OPTION_ARG_INT, &opt_start,
- "Starting handle(optional)", "0x0001" },
+ "Starting handle (optional)", "0x0001" },
{ "end", 'e' , 0, G_OPTION_ARG_INT, &opt_end,
- "Ending handle(optional)", "0xffff" },
+ "Ending handle (optional)", "0xffff" },
{ "uuid", 'u', G_OPTION_FLAG_OPTIONAL_ARG, G_OPTION_ARG_CALLBACK,
- parse_uuid, "UUID16 or UUID128(optional)", "0x1801"},
+ parse_uuid, "UUID16 or UUID128 (optional)", "0x1801"},
{ NULL },
};
static GOptionEntry char_rw_options[] = {
{ "handle", 'a' , 0, G_OPTION_ARG_INT, &opt_handle,
- "Read/Write characteristic by handle(required)", "0x0001" },
+ "Read/Write characteristic by handle (required)", "0x0001" },
{ "value", 'n' , 0, G_OPTION_ARG_STRING, &opt_value,
"Write characteristic value (required for write operation)",
"0x0001" },
--
2.38.1
next reply other threads:[~2023-02-12 17:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-12 17:24 David Nicolson [this message]
2023-02-12 18:51 ` [BlueZ] gatttool: Use consistent spacing before brackets bluez.test.bot
2023-02-14 20:40 ` [PATCH BlueZ] " patchwork-bot+bluetooth
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=20230212172402.19018-1-david.nicolson@gmail.com \
--to=david.nicolson@gmail.com \
--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 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.