This bug was fixed in the package blktap-dkms - 2.0.93-0.6ubuntu1
---------------
blktap-dkms (2.0.93-0.6ubuntu1) yakkety; urgency=low
* Merge from Debian unstable (LP: #1599127). Remaining changes:
- debian/ubuntu_control_vars: Stop recommending kernel headers, our DKMS
packages shouldn't do this, as we have no way of matching installed
kernel.
- Substitute linux-any for the list of architectures.
* d/p/follow-block_device_operations-release-return-void.patch -- follow
upstream interface changes in block_device_operations.
blktap-dkms (2.0.93-0.6) unstable; urgency=medium
* Non-maintainer upload.
* Follow changes in mainline 4.4 which moves to
using gfpflags_allow_blocking() to identify critical
sections. Thanks to Andy Whitcroft <[email protected]>
(Closes: #813678)
-- Andy Whitcroft <[email protected]> Tue, 05 Jul 2016 12:23:09 +0100
** Changed in: blktap-dkms (Ubuntu)
Status: In Progress => 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/1599127
Title:
blktap-dkms: merge debian 2.0.93-0.6
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/blktap-dkms/+bug/1599127/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
