All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 220398] Bluetooth devices experience severe connection issues, frequent disconnections, and input lag in kernel 6.15.2, working fine in 6.15.1.
Date: Sun, 03 Aug 2025 08:40:45 +0000	[thread overview]
Message-ID: <bug-220398-62941-dWvBPg0d4L@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220398-62941@https.bugzilla.kernel.org/>

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

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 the report. Looking through the commits between v6.15.1 and
v6.15.2, the only Bluetooth change is related to Qualcomm:

    $ git log --oneline v6.15.1..v6.15.2 drivers/bluetooth/
    8b91e4b6b82b5 Bluetooth: hci_qca: move the SoC type check to the right
place

Too speed up fixing this, could you bisect the commit [1]?

https://docs.kernel.org/admin-guide/verify-bugs-and-bisect-regressions.html#v

-- 
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:[~2025-08-03  8:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-03  0:16 [Bug 220398] New: Bluetooth devices experience severe connection issues, frequent disconnections, and input lag in kernel 6.15.2, working fine in 6.15.1 bugzilla-daemon
2025-08-03  8:40 ` bugzilla-daemon [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=bug-220398-62941-dWvBPg0d4L@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 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.