From: Alain Michaud <alainm@chromium.org>
To: linux-bluetooth@vger.kernel.org
Cc: Alain Michaud <alainm@chromium.org>
Subject: [BlueZ PATCH v1] Fixing opcode definition order
Date: Mon, 4 May 2020 15:31:34 +0000 [thread overview]
Message-ID: <20200504153134.226879-1-alainm@chromium.org> (raw)
Fixing what looks like a bad merge in the opcode order.
---
lib/mgmt.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/lib/mgmt.h b/lib/mgmt.h
index e46e08ba8..c81286460 100644
--- a/lib/mgmt.h
+++ b/lib/mgmt.h
@@ -586,6 +586,8 @@ struct mgmt_cp_set_phy_confguration {
#define MGMT_OP_SET_BLOCKED_KEYS 0x0046
+#define MGMT_OP_SET_WIDEBAND_SPEECH 0x0047
+
#define MGMT_OP_READ_SECURITY_INFO 0x0048
struct mgmt_rp_read_security_info {
uint16_t sec_len;
@@ -606,8 +608,6 @@ struct mgmt_cp_set_blocked_keys {
struct mgmt_blocked_key_info keys[0];
} __packed;
-#define MGMT_OP_SET_WIDEBAND_SPEECH 0x0047
-
#define MGMT_EV_CMD_COMPLETE 0x0001
struct mgmt_ev_cmd_complete {
uint16_t opcode;
--
2.26.2.526.g744177e7f7-goog
next reply other threads:[~2020-05-04 15:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 15:31 Alain Michaud [this message]
2020-05-04 15:33 ` [BlueZ PATCH v1] Fixing opcode definition order Alain Michaud
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=20200504153134.226879-1-alainm@chromium.org \
--to=alainm@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).