I think this is a wontfix for oem-5.6 at this point

** Changed in: linux-oem-5.6 (Ubuntu Groovy)
       Status: New => Invalid

** Changed in: linux-oem-5.6 (Ubuntu)
       Status: New => Won't Fix

** Changed in: linux-oem-5.6 (Ubuntu Focal)
       Status: In Progress => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1895073

Title:
  Thunderbolt Authenticate on disconnect patches

Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.6 package in Ubuntu:
  Won't Fix
Status in linux source package in Focal:
  New
Status in linux-oem-5.6 source package in Focal:
  Won't Fix
Status in linux source package in Groovy:
  In Progress
Status in linux-oem-5.6 source package in Groovy:
  Invalid

Bug description:
  [Impact]
  These two patches is provided by Mario Limonciello and have landed in 5.9-rc1.
  Support a better flow for authenticate of TBT dock on disconnect
  *thunderbolt: Add support for separating the flush to SPI and authenticate    
                                                             
  *thunderbolt: Add support for authenticate on disconnect    

  Also need the following patches.
  thunderbolt: Ensure left shift of 512 does not overflow a 32 bit int
  thunderbolt: Add support for on-board retimers
  thunderbolt: Implement USB3 bandwidth negotiation routines
  thunderbolt: Split common NVM functionality into a separate file
  thunderbolt: Generalize usb4_switch_do_[read|write]_data()
  thunderbolt: Implement USB4 port sideband operations for retimer access

  [Fix]

  [Test]

  [Regression]
  Low, the patches have landed in 5.9-rc1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895073/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to