From: Alain Michaud <alainm@chromium.org>
To: linux-bluetooth@vger.kernel.org
Cc: Alain Michaud <alainm@chromium.org>
Subject: [BlueZ PATCH v2] Fixing opcode definition order
Date: Mon, 4 May 2020 15:36:26 +0000 [thread overview]
Message-ID: <20200504153626.231603-1-alainm@chromium.org> (raw)
Fixing what looks like a bad merge in the opcode order.
Signed-off-by: Alain Michaud <alainm@chromium.org>
---
lib/mgmt.h | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/lib/mgmt.h b/lib/mgmt.h
index e46e08ba8..0722c5206 100644
--- a/lib/mgmt.h
+++ b/lib/mgmt.h
@@ -586,15 +586,11 @@ struct mgmt_cp_set_phy_confguration {
#define MGMT_OP_SET_BLOCKED_KEYS 0x0046
-#define MGMT_OP_READ_SECURITY_INFO 0x0048
-struct mgmt_rp_read_security_info {
- uint16_t sec_len;
- uint8_t sec[0];
-} __packed;
+#define MGMT_OP_SET_WIDEBAND_SPEECH 0x0047
#define HCI_BLOCKED_KEY_TYPE_LINKKEY 0x00
-#define HCI_BLOCKED_KEY_TYPE_LTK 0x01
-#define HCI_BLOCKED_KEY_TYPE_IRK 0x02
+#define HCI_BLOCKED_KEY_TYPE_LTK 0x01
+#define HCI_BLOCKED_KEY_TYPE_IRK 0x02
struct mgmt_blocked_key_info {
uint8_t type;
@@ -606,7 +602,11 @@ struct mgmt_cp_set_blocked_keys {
struct mgmt_blocked_key_info keys[0];
} __packed;
-#define MGMT_OP_SET_WIDEBAND_SPEECH 0x0047
+#define MGMT_OP_READ_SECURITY_INFO 0x0048
+struct mgmt_rp_read_security_info {
+ uint16_t sec_len;
+ uint8_t sec[0];
+} __packed;
#define MGMT_EV_CMD_COMPLETE 0x0001
struct mgmt_ev_cmd_complete {
--
2.26.2.526.g744177e7f7-goog
next reply other threads:[~2020-05-04 15:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 15:36 Alain Michaud [this message]
2020-05-05 20:58 ` [BlueZ PATCH v2] Fixing opcode definition order Marcel Holtmann
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=20200504153626.231603-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 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.