public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 219365] USB bluetooth dongle stop working after upgrade from 6.11.1 to 6.11.2
Date: Wed, 09 Oct 2024 08:47:28 +0000	[thread overview]
Message-ID: <bug-219365-62941-SceBOU2Q3E@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219365-62941@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=219365

Paul Menzel (pmenzel+bugzilla.kernel.org@molgen.mpg.de) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pmenzel+bugzilla.kernel.org
                   |                            |@molgen.mpg.de

--- Comment #1 from Paul Menzel (pmenzel+bugzilla.kernel.org@molgen.mpg.de) ---
Thank you for your report, and great that you can build the Linux kernel
yourself.

> Maybe is one or all commits has caused the regression on my BT dongle

It’d be great if you tested each of the three commits. (Normally, `git bisect
start -- drivers/bluetooth/btusb.c net/bluetooth/`, and then `git bisect good
v6.11.1` and `git bisect bad v6.11.2`, would do that automatically.)

If you already have git clone, then:

    git remote add stable
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
    git fetch stable

or, if you do not,

    git clone
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git

Then

    git reset --hard f68f72d04b60d3af36b63b888fe084966bca07b9

build and test. If it does *not* work, it’s the fault commit.

Then

    git reset --hard 846a6fc7860119ee72737391856497b3fcf7c2b5

If it does *not* work, it’s the fault commit.

Then

    git reset --hard 8603daa4300b84abb3c68e48f3b607d7d5a2a207

If it does *not* work, it’s the fault commit.

It’d be also good to know, if it works with current Linux master branch, or
6.12-rc2.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

  reply	other threads:[~2024-10-09  8:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-09  4:50 [Bug 219365] New: USB bluetooth dongle stop working after upgrade from 6.11.1 to 6.11.2 bugzilla-daemon
2024-10-09  8:47 ` bugzilla-daemon [this message]
2024-10-09 17:53 ` [Bug 219365] " bugzilla-daemon
2024-10-09 18:06 ` bugzilla-daemon
2024-10-09 18:14 ` bugzilla-daemon
2024-10-09 18:19 ` bugzilla-daemon
2024-10-09 18:25 ` bugzilla-daemon
2024-10-10  3:04 ` bugzilla-daemon
2024-10-10  3:05 ` bugzilla-daemon
2024-10-10  3:08 ` bugzilla-daemon
2024-10-15 15:38 ` bugzilla-daemon
2024-10-16  0:34 ` bugzilla-daemon
2024-10-22 22:49 ` bugzilla-daemon
2025-02-26 23:55 ` 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-219365-62941-SceBOU2Q3E@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