From: Andrew Drake <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] a69fa6: adapter: Fix advertising monitor on Linux 5.12-5.17
Date: Wed, 13 Jul 2022 14:42:02 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/163de8-a69fa6@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: a69fa692b094347e3a1dbcd9198d426f671dec0c
https://github.com/bluez/bluez/commit/a69fa692b094347e3a1dbcd9198d426f671dec0c
Author: Andrew Drake <adrake@adrake.org>
Date: 2022-07-13 (Wed, 13 Jul 2022)
Changed paths:
M src/adapter.c
Log Message:
-----------
adapter: Fix advertising monitor on Linux 5.12-5.17
The existing code assumes that, if a device supports advertising monitor
offload, DEVICE_FOUND events can be ignored since the kernel will send
ADV_MONITOR_DEVICE_FOUND events instead. Unfortunately, these new events
were added in 5.18, but offload was added in 5.12. This patch adds a
check on the MGMT API version so we can process the older DEVICE_FOUND
events when the new events are not supported.
Fixes: https://github.com/bluez/bluez/issues/357
reply other threads:[~2022-07-13 21:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bluez/bluez/push/refs/heads/master/163de8-a69fa6@github.com \
--to=noreply@github.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).