From: "Jonas Dreßler" <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 7ef406: client: Invalidate scan filter on "scan" command
Date: Mon, 13 Nov 2023 11:37:55 -0800 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/b978f9-7ef406@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 7ef40617a049f083b3b5d318bcecbc60c4673c13
https://github.com/bluez/bluez/commit/7ef40617a049f083b3b5d318bcecbc60c4673c13
Author: Jonas Dreßler <verdre@v0yd.nl>
Date: 2023-11-13 (Mon, 13 Nov 2023)
Changed paths:
M client/main.c
Log Message:
-----------
client: Invalidate scan filter on "scan" command
The "scan bredr" and "scan le" commands are broken right now because the
transport filter gets set, but not actually invalidated.
Invalidate the filter with `filter.set = false` so that it actually gets
updated when set_discovery_filter() is called afterwards.
reply other threads:[~2023-11-13 19:37 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/b978f9-7ef406@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