This bug was fixed in the package linux-gcp - 5.0.0-1020.20~18.04.1
---
linux-gcp (5.0.0-1020.20~18.04.1) bionic; urgency=medium
* bionic/linux-gcp: 5.0.0-1020.20~18.04.1 -proposed tracker (LP:
#1846012)
[ Ubuntu: 5.0.0-1020.20 ]
* disco/linux-gcp: 5.0.0-1020.20 -proposed
This bug was fixed in the package linux-gcp - 4.15.0-1046.49
---
linux-gcp (4.15.0-1046.49) xenial; urgency=medium
* xenial/linux-gcp: 4.15.0-1046.49 -proposed tracker (LP: #1845815)
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
* Enable napi_tx
This bug was fixed in the package linux-gke-4.15 - 4.15.0-1045.48
---
linux-gke-4.15 (4.15.0-1045.48) bionic; urgency=medium
* bionic/linux-gke-4.15: 4.15.0-1045.48 -proposed tracker (LP:
#1844382)
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
*
** Changed in: linux-gcp (Ubuntu Disco)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834681
Title:
Enable napi_tx for GCP/GKE kernels
To manage
** Also affects: linux-gcp (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux-gke-5.0 (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux-gcp (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux-gke-5.0 (Ubuntu
This likely looks confusing but the bionic/gcp kernel (rolled to 5.0) is
based on the disco/gcp kernel, so the patch(es) only need to go to disco
and then come back automatically.
** Also affects: linux-gke-5.0 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-gcp
