Linux bluetooth development
 help / color / mirror / Atom feed
* [PATCH BlueZ 1/3] mgmt-api: Update Device Found Event documentation
@ 2023-06-20 20:40 Luiz Augusto von Dentz
  2023-06-20 20:40 ` [PATCH BlueZ 2/3] monitor: Add missing flags to MGMT Device Found Event Luiz Augusto von Dentz
                   ` (3 more replies)
  0 siblings, 4 replies; 5+ messages in thread
From: Luiz Augusto von Dentz @ 2023-06-20 20:40 UTC (permalink / raw)
  To: linux-bluetooth

From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>

This updates Device Found Event documentation to mention the new flag
introduced to track when the event is generated due a interleaved Scan
Response that couldn't be merged.
---
 doc/mgmt-api.txt | 1 +
 1 file changed, 1 insertion(+)

diff --git a/doc/mgmt-api.txt b/doc/mgmt-api.txt
index c7191a028238..59e61d361dc2 100644
--- a/doc/mgmt-api.txt
+++ b/doc/mgmt-api.txt
@@ -4399,6 +4399,7 @@ Device Found Event
 		2	Not Connectable
 		3	Reserved (not in use)
 		4	Name Request Failed
+		5	Scan Response
 
 	For the RSSI field a value of 127 indicates that the RSSI is
 	not available. That can happen with Bluetooth 1.1 and earlier
-- 
2.40.1


^ permalink raw reply related	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2023-06-21 22:10 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-06-20 20:40 [PATCH BlueZ 1/3] mgmt-api: Update Device Found Event documentation Luiz Augusto von Dentz
2023-06-20 20:40 ` [PATCH BlueZ 2/3] monitor: Add missing flags to MGMT Device Found Event Luiz Augusto von Dentz
2023-06-20 20:40 ` [PATCH BlueZ 3/3] adapter: Handle Device Found Event with Scan Response flag Luiz Augusto von Dentz
2023-06-20 22:31 ` [BlueZ,1/3] mgmt-api: Update Device Found Event documentation bluez.test.bot
2023-06-21 22:10 ` [PATCH BlueZ 1/3] " patchwork-bot+bluetooth

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox