This bug was fixed in the package linux-hwe-edge - 5.3.0-19.20~18.04.2
---------------
linux-hwe-edge (5.3.0-19.20~18.04.2) bionic; urgency=medium
* Packaging resync (LP: #1786013)
- update dkms package versions
linux-hwe-edge (5.3.0-19.20~18.04.1) bionic; urgency=medium
* bionic/linux-hwe-edge: 5.3.0-19.20~18.04.1 -proposed tracker (LP:
#1848645)
* linux won't build when new virtualbox version is present on the archive
(LP: #1848788)
- [Packaging]: download virtualbox from sources
[ Ubuntu: 5.3.0-19.20 ]
* eoan/linux: 5.3.0-19.20 -proposed tracker (LP: #1848648)
* eoan kernel does not contain "ipv6: do not free rt if FIB_LOOKUP_NOREF is
set on suppress rule" (LP: #1847478)
- ipv6: do not free rt if FIB_LOOKUP_NOREF is set on suppress rule
linux-hwe-edge (5.3.0-18.19~18.04.2) bionic; urgency=medium
* Drop i386 build for 19.10 (LP: #1845714)
- [Debian] Reintroduce support for producing i386 kernels
-- Thadeu Lima de Souza Cascardo <[email protected]> Tue, 22 Oct
2019 11:59:21 -0300
** Changed in: linux-hwe-edge (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1820868
Title:
bionic: fork out linux-snapdragon into its own topic kernel
Status in linux package in Ubuntu:
Fix Released
Status in linux-meta package in Ubuntu:
Fix Released
Status in linux-snapdragon package in Ubuntu:
Fix Committed
Status in linux source package in Bionic:
Fix Released
Status in linux-hwe-edge source package in Bionic:
Fix Released
Status in linux-meta source package in Bionic:
Fix Released
Status in linux-snapdragon source package in Bionic:
Fix Released
Bug description:
Impact:
During the Bionic cycle, a decision was made to incorporate the
linux-snapdragon
kernel into the master branch, thus reducing the number of topic kernels and
the
stable maintenance burden.
But as time passed and new patches were produced by Qualcomm, incorporating
them
into master while avoiding to destabilize generic became more and more
problematic, down to the point where it was not a viable approach
anymore.
At that point, the decision was made to fork out linux-snapdragon into its own
topic kernel (e.g. linux-raspi2), giving more room to incorporate new code
coming from the Qualcomm tree and avoiding to destabilize any other target in
generic.
Fix:
This is a three step process:
1) disable building linux-snapdragon from master by applying the attached
patch
to bionic/master
2) create a new bionic/linux-snapdragon branch and reset hard to my
lp:snapdragon-topic-kernel branch (see below)
3) update bionic-meta to point to the new bionic/linux-snapdragon
kernel
Regression potential
From the point of view of bionic/master, this pull request doesn't introduce
any
substantial change, and in the future will let us purge generic from several
external patches.
While from the point of view of linux-snapdragon, with ~600 code commits and
~4k
config changes, this represent a brand new kernel and while great care was
used
while putting together this branch, there's clearly a regression potential
here
but we can't leave linux-snapdragon stagnate behind the curve, so the sooner
we
bite the bullet, the better we can the deal with the eventual fallout.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820868/+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
