This bug was fixed in the package linux - 4.2.0-14.16 --------------- linux (4.2.0-14.16) wily; urgency=low
[ Tim Gardner ] * Release Tracking Bug - LP: #1501818 * rebase to v4.2.2 * [Config] CONFIG_RTC_DRV_XGENE=y - LP: #1499869 [ Upstream Kernel Changes ] * mei: do not access freed cb in blocking write - LP: #1494076 * mei: bus: fix drivers and devices names confusion - LP: #1494076 * mei: bus: rename nfc.c to bus-fixup.c - LP: #1494076 * mei: bus: move driver api functions at the start of the file - LP: #1494076 * mei: bus: rename uevent handler to mei_cl_device_uevent - LP: #1494076 * mei: bus: don't enable events implicitly in device enable - LP: #1494076 * mei: bus: report if event registration failed - LP: #1494076 * mei: bus: revamp device matching - LP: #1494076 * mei: bus: revamp probe and remove functions - LP: #1494076 * mei: bus: add reference to bus device in struct mei_cl_client - LP: #1494076 * mei: bus: add me client device list infrastructure - LP: #1494076 * mei: bus: enable running fixup routines before device registration - LP: #1494076 * mei: bus: blacklist the nfc info client - LP: #1494076 * mei: bus: blacklist clients by number of connections - LP: #1494076 * mei: bus: simplify how we build nfc bus name - LP: #1494076 * mei: bus: link client devices instead of host clients - LP: #1494076 * mei: support for dynamic clients - LP: #1494076 * mei: disconnect on connection request timeout - LP: #1494076 * mei: define async notification hbm commands - LP: #1494076 * mei: implement async notification hbm messages - LP: #1494076 * mei: enable async event notifications only from hbm version 2.0 - LP: #1494076 * mei: add mei_cl_notify_request command - LP: #1494076 * mei: add a handler that waits for notification on event - LP: #1494076 * mei: add async event notification ioctls - LP: #1494076 * mei: support polling for event notification - LP: #1494076 * mei: implement fasync for event notification - LP: #1494076 * mei: bus: add and call callback on notify event - LP: #1494076 * mei: hbm: add new error code MEI_CL_CONN_NOT_ALLOWED - LP: #1494076 * mei: me: d0i3: add the control registers - LP: #1494076 * mei: me: d0i3: add flag to indicate D0i3 support - LP: #1494076 * mei: me: d0i3: enable d0i3 interrupts - LP: #1494076 * mei: hbm: reorganize the power gating responses - LP: #1494076 * mei: me: d0i3: add d0i3 enter/exit state machine - LP: #1494076 * mei: me: d0i3: move mei_me_hw_reset down in the file - LP: #1494076 * mei: me: d0i3: exit d0i3 on driver start and enter it on stop - LP: #1494076 * mei: me: add sunrise point device ids - LP: #1494076 * mei: hbm: bump supported HBM version to 2.0 - LP: #1494076 * mei: remove check on pm_runtime_active in __mei_cl_disconnect - LP: #1494076 * mei: fix debugfs files leak on error path - LP: #1494076 [ Upstream Kernel Changes ] * rebase to v4.2.2 - LP: #1492132 -- Tim Gardner <tim.gard...@canonical.com> Tue, 29 Sep 2015 09:02:13 -0700 ** Changed in: linux (Ubuntu Wily) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1500672 Title: cpufreq: powernv : Decrease the severity of console messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs