From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 217651] BCM20702B0 Bluetooth device in MacBook no longer working
Date: Tue, 11 Jul 2023 14:37:46 +0000 [thread overview]
Message-ID: <bug-217651-62941-SKvR2l4ezI@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217651-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=217651
The Linux kernel's regression tracker (Thorsten Leemhuis) (regressions@leemhuis.info) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |regressions@leemhuis.info
--- Comment #12 from The Linux kernel's regression tracker (Thorsten Leemhuis) (regressions@leemhuis.info) ---
(In reply to johnbholland from comment #10)
> I've chosen a commit from before that and am trying to
> build that and test it. If it boots and the bluetooth works, I guess
> 6.4.0-rc1 and that starting point could be initial points to use in
> bisecting?
Thanks for trying to find the cause, that helpful and simply needed in cases
like this. You might want to bisect between 6.3 and 6.4, as maybe it's some
change outside of bluetooth that broke things (but it's possible that you are
on the right track, too).
Side notes:
* might be worth giving 6.5-rc1 a try, with a bit of luck it might contain a
fix (but there is a decent chance we are unlucky).
* cross-compiling might help to speed things up.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2023-07-11 14:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-09 22:56 [Bug 217651] New: BCM20702B0 Bluetooth device in MacBook no longer working bugzilla-daemon
2023-07-09 22:57 ` [Bug 217651] " bugzilla-daemon
2023-07-10 3:33 ` bugzilla-daemon
2023-07-10 12:08 ` bugzilla-daemon
2023-07-10 12:09 ` bugzilla-daemon
2023-07-10 12:09 ` bugzilla-daemon
2023-07-10 12:10 ` bugzilla-daemon
2023-07-10 12:11 ` bugzilla-daemon
2023-07-10 12:13 ` bugzilla-daemon
2023-07-10 12:14 ` bugzilla-daemon
2023-07-10 18:50 ` bugzilla-daemon
2023-07-11 1:18 ` bugzilla-daemon
2023-07-11 14:37 ` bugzilla-daemon [this message]
2023-07-11 16:13 ` bugzilla-daemon
2023-07-12 22:59 ` bugzilla-daemon
2023-07-12 23:13 ` [Bug,217651] " bluez.test.bot
2023-07-13 4:18 ` [Bug 217651] " bugzilla-daemon
2023-07-13 5:36 ` bugzilla-daemon
2023-07-13 5:45 ` bugzilla-daemon
2023-07-13 6:17 ` [Bug,217651] " bluez.test.bot
2023-07-13 5:58 ` [Bug 217651] " bugzilla-daemon
2023-07-13 11:31 ` bugzilla-daemon
2023-07-13 11:46 ` bugzilla-daemon
2023-07-13 11:54 ` bugzilla-daemon
2023-07-13 12:24 ` [Bug,217651] " bluez.test.bot
2023-08-28 20:34 ` [Bug 217651] " bugzilla-daemon
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=bug-217651-62941-SKvR2l4ezI@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--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).