Public bug reported:

We applied a set of patches early as the upstreaming got delayed. The
patch now is in linux-next on its way into upstream linux. When that
happens we want to replace the SAUCE patch by its upstream version (for
example to get security checks right).

“UBUNTU: SAUCE: thunderbolt: Add DP out resource when DP tunnel is
discovered.”

 to be replaced by:

commit b60e31bf18a7064032dbcb73dcb5b58f8a00a110 linux-next
 “thunderbolt: Add DP OUT resource when DP tunnel is discovered”

By now it is confirmed that the patch in linux-next is somehow different
from the one we carry. But to be on the safe side we should wait until
it is really upstream and maybe give a little time to settle before
actually changing things.

** Affects: linux (Ubuntu)
     Importance: Medium
     Assignee: Stefan Bader (smb)
         Status: Triaged

** Affects: linux (Ubuntu Jammy)
     Importance: Medium
         Status: Confirmed

** Also affects: linux (Ubuntu Jammy)
   Importance: Undecided
       Status: New

** Changed in: linux (Ubuntu Jammy)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Jammy)
       Status: New => Confirmed

-- 
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/1989944

Title:
  [22.04/Jammy] Replace SAUCE AMD DP tunneling patch by upstream version

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Jammy:
  Confirmed

Bug description:
  We applied a set of patches early as the upstreaming got delayed. The
  patch now is in linux-next on its way into upstream linux. When that
  happens we want to replace the SAUCE patch by its upstream version
  (for example to get security checks right).

  “UBUNTU: SAUCE: thunderbolt: Add DP out resource when DP tunnel is
  discovered.”

   to be replaced by:

  commit b60e31bf18a7064032dbcb73dcb5b58f8a00a110 linux-next
   “thunderbolt: Add DP OUT resource when DP tunnel is discovered”

  By now it is confirmed that the patch in linux-next is somehow
  different from the one we carry. But to be on the safe side we should
  wait until it is really upstream and maybe give a little time to
  settle before actually changing things.

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


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to