linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 216817] btusb device with ID 0489:e0d0 no longer working after v6.0
Date: Thu, 26 Jan 2023 16:21:49 +0000	[thread overview]
Message-ID: <bug-216817-62941-BkVYH9aEse@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216817-62941@https.bugzilla.kernel.org/>

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

Mario Limonciello (AMD) (mario.limonciello@amd.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |CODE_FIX

--- Comment #12 from Mario Limonciello (AMD) (mario.limonciello@amd.com) ---
As this is upstreamed as of 6.2-rc5 (3a4d29b6d631b ("Bluetooth: hci_sync: Fix
use HCI_OP_LE_READ_BUFFER_SIZE_V2")) closing this issue.

The fix should trickle into 6.1.y as well.

-- 
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:[~2023-01-26 16:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-18  4:28 [Bug 216817] New: btusb device with ID 0489:e0d0 no longer working after v6.0 bugzilla-daemon
2022-12-18  4:30 ` [Bug 216817] " bugzilla-daemon
2022-12-19  8:33 ` bugzilla-daemon
2022-12-19 10:55 ` bugzilla-daemon
2022-12-19 21:06 ` bugzilla-daemon
2022-12-19 21:10 ` bugzilla-daemon
2022-12-19 21:13   ` [Bug,216817] " bluez.test.bot
2022-12-20  3:25 ` [Bug 216817] " bugzilla-daemon
2022-12-20 20:25 ` bugzilla-daemon
2022-12-21 11:19 ` bugzilla-daemon
2023-01-11 19:44 ` bugzilla-daemon
2023-01-11 19:44 ` bugzilla-daemon
2023-01-16 13:29 ` bugzilla-daemon
2023-01-17 19:22 ` bugzilla-daemon
2023-01-26 16:21 ` 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-216817-62941-BkVYH9aEse@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).