All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 221637] Regression for Intel Corporation Device a876 (rev 10)
Date: Sun, 14 Jun 2026 23:41:29 +0000	[thread overview]
Message-ID: <bug-221637-62941-gSxdco6tgJ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221637-62941@https.bugzilla.kernel.org/>

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

Kiran (kiran.k@intel.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kiran.k@intel.com

--- Comment #7 from Kiran (kiran.k@intel.com) ---
Hi Biance, Paul,

Appreciate if you can test and feedback with the below patch.

https://kernel.googlesource.com/pub/scm/linux/kernel/git/bluetooth/bluetooth-next/+/5917dd39db2bfc8b1b4c6ea8ed99adb4badef707

Seeing the error pattern in dmesg, appears like the issue has been fixed
already and the patch is present in bluetooth-next,

Thanks,
Kiran

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

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

  parent reply	other threads:[~2026-06-14 23:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-10 19:46 [Bug 221637] New: Regression for Intel Corporation Device a876 (rev 10) bugzilla-daemon
2026-06-10 20:03 ` [Bug 221637] " bugzilla-daemon
2026-06-11 14:29 ` bugzilla-daemon
2026-06-11 14:36 ` bugzilla-daemon
2026-06-11 14:41 ` bugzilla-daemon
2026-06-11 17:18 ` bugzilla-daemon
2026-06-12  6:57 ` bugzilla-daemon
2026-06-14  7:04 ` bugzilla-daemon
2026-06-14 23:41 ` bugzilla-daemon [this message]
2026-06-15  5:48 ` bugzilla-daemon
2026-06-15 14:49 ` 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-221637-62941-gSxdco6tgJ@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.