From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH BlueZ] monitor/att: Fix decoding for notifications
Date: Mon, 13 Jun 2022 16:34:19 -0700 [thread overview]
Message-ID: <20220613233419.177421-2-luiz.dentz@gmail.com> (raw)
In-Reply-To: <20220613233419.177421-1-luiz.dentz@gmail.com>
From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
---
monitor/att.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/monitor/att.c b/monitor/att.c
index 00db8ddaa..de70a9dc4 100644
--- a/monitor/att.c
+++ b/monitor/att.c
@@ -1547,7 +1547,7 @@ static void print_notify(const struct l2cap_frame *frame, uint16_t handle,
return;
}
- attr = get_attribute(frame, handle, false);
+ attr = get_attribute(frame, handle, true);
if (!attr)
return;
--
2.35.3
next prev parent reply other threads:[~2022-06-13 23:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 23:34 [PATCH BlueZ] device: Add connectable flag to bearer state Luiz Augusto von Dentz
2022-06-13 23:34 ` Luiz Augusto von Dentz [this message]
2022-06-14 0:39 ` [BlueZ] monitor/att: Fix decoding for notifications bluez.test.bot
2022-06-14 20:50 ` [PATCH BlueZ] " patchwork-bot+bluetooth
2022-06-14 0:43 ` [BlueZ] device: Add connectable flag to bearer state 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=20220613233419.177421-2-luiz.dentz@gmail.com \
--to=luiz.dentz@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 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).