commit 68e5e9d734503695915734e50e9427624cf8f3b2 (Re: vfb: make virtual framebuffer mmapable)

From: Jan Beulich
Date: Fri Oct 02 2009 - 06:19:23 EST


Is there any particular reason why this change uses vmalloc_32()
rather than simply vmalloc()? I can't see why the underlying physical
address width would matter here in any way...

Thanks, Jan

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/