Like I said, -29 was basically renamed to -31. It HAS been fixed since -29 (now
-31)
On Tuesday, December 13, 2016 11:42:11 PM EST Scott Cowles Jacobs wrote:
> The Linux changelog people seem a bit comfused...
>
> I just received Linux 4.8.0-31.33,
> and ITS changlog says:
>
> " * Yakkety upd
4.8.0-29 does/did indeed include the fix but never made it out of
proposed and has since been bumped to -31
On Dec 12, 2016, Scott Cowles Jacobs <1630...@bugs.launchpad.net> wrote:
>>4.8.0-30 does not have the 4.8.11 update. It's still at 4.8.6
>
>Is "Michael Bock (michi-bock)" referring to a diff
4.8.0-30 does not have the 4.8.11 update. It's still at 4.8.6. It's been
pushed back to 4.8.0-31
https://people.canonical.com/~kernel/info/kernel-version-map.html
On Sunday, December 11, 2016 12:01:45 PM EST Michael Bock wrote:
> Sorry, but updating to 4.8.0-30-generic yesterday still didn't sol
The fix is in the current 4.8 stable rc.
On Nov 10, 2016 2:25 AM, "Graham Inggs" wrote:
> Looks like it was accepted here:
> https://github.com/torvalds/linux/commit/ed6d6f8f42d7302f6f9b6245f34927
> ec20d26c12
>
> We still need this to go into the yakkety 4.8 kernel.
>
> --
> You received this b
