From: "Kenneth R. Crudup" <kenny@panix.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: Luiz Augusto Von Dentz <luiz.von.dentz@intel.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
"Kenneth R. Crudup" <kenny@panix.com>
Subject: Re: Commit ad383c2c6 ("Bluetooth: hci_sync: Enable advertising when LL privacy is enabled") breaks my MS ArcTouch mouse
Date: Sat, 29 Jan 2022 14:07:00 -0800 (PST) [thread overview]
Message-ID: <3bc9bbab-b3cd-4c52-cc33-5d723d973deb@panix.com> (raw)
In-Reply-To: <6f3b9dbb-6ecf-cfea-2127-cb3360d78431@panix.com>
So, it turns out that my lack of discoverability is also tied into this last
series of BT commits (and apparently the result of some commit other than the
one named in the Subject: line); while I could take the time to bisect this
issue as well, seems to me that something as basic as not being able to put
an HCI adapter in discoverable mode is a pretty big regression (especially
on something as ubiquitous as Intel BT adapters) that I can't be the only
one who's seeing these issues- have there been any other reports, and are
there any fixes upcoming?
-Kenny
--
Kenneth R. Crudup / Sr. SW Engineer, Scott County Consulting, Orange County CA
next prev parent reply other threads:[~2022-01-29 22:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-23 1:51 Commit ad383c2c6 ("Bluetooth: hci_sync: Enable advertising when LL privacy is enabled") breaks my MS ArcTouch mouse Kenneth R. Crudup
2022-01-24 19:45 ` Luiz Augusto von Dentz
2022-01-24 19:59 ` Kenneth R. Crudup
2022-01-25 1:13 ` Luiz Augusto von Dentz
2022-01-25 1:27 ` Kenneth R. Crudup
2022-01-25 1:29 ` Kenneth R. Crudup
2022-01-25 1:51 ` Kenneth R. Crudup
2022-01-27 20:58 ` Kenneth R. Crudup
2022-01-29 22:07 ` Kenneth R. Crudup [this message]
2022-03-05 0:03 ` Kenneth R. Crudup
2022-03-05 1:10 ` Luiz Augusto von Dentz
2022-03-05 2:28 ` Kenneth R. Crudup
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=3bc9bbab-b3cd-4c52-cc33-5d723d973deb@panix.com \
--to=kenny@panix.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=luiz.von.dentz@intel.com \
/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.