Hi Greg,
These are the part III commits that I've analized from the list of
upstream commits that have been backported to 3.2 but missing from 3.4.
For the 11 commits,
- 8 commits were marked for stable but can't be applied cleanly to
3.4.x.
- 3 commits have not stable tag. They're 2 prerequisites and 1 bugfix. I've
found out why it was backported to 3.2.x and I'm sure should be applied to
3.4.x.
Please cherry-pick these commits from 3.2.x:
788c8de383e3 virtio_blk: Drop unused request tracking list
e5000b33460e virtio-blk: Fix hot-unplug race in remove method
88963fd6c66b virtio-blk: Call del_gendisk() before disable guest kick
95964784565a virtio-blk: Reset device after blk_cleanup_queue()
fcb8996728fb mm: add kmap_to_page()
8bc528cece6b mm: highmem: export kmap_to_page for modules
30d395b124c5 virtio: 9p: correctly pass physical address to userspace for
high pages
63dddb4936fa virtio-blk: Don't free ida when disk is in use
0cbb6f3def0c virtio_console: fix uapi header
There are other 2 commits that need some adjustments. I'll send
out the backports.
drivers/block/virtio_blk.c | 20 ++++++++++++--------
drivers/char/virtio_console.c | 20 +++++++-------------
include/linux/highmem.h | 7 -------
include/linux/virtio_console.h | 2 +-
mm/highmem.c | 13 -------------
net/9p/trans_virtio.c | 3 +--
6 files changed, 21 insertions(+), 44 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
