[Bug 1908150] Re: Groovy update: upstream stable patchset 2020-12-14

2022-03-16 Thread Po-Hsu Lin
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908150 Title: Groovy update: upstream stable patchset 2020-12-14 To manage

[Bug 1908150] Re: Groovy update: upstream stable patchset 2020-12-14

2021-02-04 Thread William Breathitt Gray
** Also affects: linux-aws (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908150 Title: Groovy update: upstream stable patchset 2020-12-14 To

[Bug 1908150] Re: Groovy update: upstream stable patchset 2020-12-14

2020-12-16 Thread Ian
** Changed in: linux (Ubuntu Groovy) 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/1908150 Title: Groovy update: upstream stable patchset 2020-12-14 To

[Bug 1908150] Re: Groovy update: upstream stable patchset 2020-12-14

2020-12-14 Thread Kamal Mostafa
Per @colin-king, we're opting to omit the v5.9 backport of: db865272d9c4 cpufreq: Avoid configuring old governors as default with intel_pstate While we evaluate the impact of: 33aa46f252c7 cpufreq: intel_pstate: Use passive mode by default without HWP -- You received this bug notification

[Bug 1908150] Re: Groovy update: upstream stable patchset 2020-12-14

2020-12-14 Thread Kamal Mostafa
** Description changed: - - SRU Justification - - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by