All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Menzel <pmenzel@molgen.mpg.de>
To: "John Holland" <johnbholland@icloud.com>,
	"Tomasz Moń" <tomasz.mon@nordicsemi.no>,
	"Luiz Augusto von Dentz" <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, regressions@lists.linux.dev,
	Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Subject: Re: bluetooth broken in Intel Macbook 2014
Date: Thu, 13 Jul 2023 06:00:08 +0200	[thread overview]
Message-ID: <552a361b-d699-5d96-543a-e3aa09e6c05c@molgen.mpg.de> (raw)
In-Reply-To: <370f0784-05c2-a36d-bfe8-f5159aeb8729@icloud.com>

[Fix email address, Cc: +regressions@lists.linux.dev, regzbot commands]

#regzbot ^introduced: c13380a55522bf14e54779a142487c224509db95
#regzot monitor: https://bugzilla.kernel.org/show_bug.cgi?id=217651

Am 13.07.23 um 01:08 schrieb John Holland:
> Hello,
> 
> I've had my first attempt at kernel development in trying to fix a 
> problem with newer kernels and the bluetooth in my Macbook Pro (2014 
> vintage). I did the bisecting and found that the commit below seems to 
> be the culprit.
> 
> 
> commit c13380a55522bf14e54779a142487c224509db95
> Author: Tomasz Moń <tomasz.mon@nordicsemi.no>
> Date:   Tue Feb 7 12:57:41 2023 +0100
> 
>     Bluetooth: btusb: Do not require hardcoded interface numbers
> ......
> 
> Reverting this change in both 6.3 and 6.5 restores my ability to use the 
> Bluetooth in this Mac. I created a bug in bugzilla for it.
> 
> 
> This is new to me, I'm a retired application developer. I hope this is 
> close enough to the correct process. Thanks,
> 
> John Holland
> 
> 
> 
> https://bugzilla.kernel.org/show_bug.cgi?id=217651

      reply	other threads:[~2023-07-13  4:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-12 23:08 bluetooth broken in Intel Macbook 2014 John Holland
2023-07-13  4:00 ` Paul Menzel [this message]

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=552a361b-d699-5d96-543a-e3aa09e6c05c@molgen.mpg.de \
    --to=pmenzel@molgen.mpg.de \
    --cc=johnbholland@icloud.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=luiz.von.dentz@intel.com \
    --cc=regressions@lists.linux.dev \
    --cc=tomasz.mon@nordicsemi.no \
    /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.