>From 43f5b3085fdd27c4edf535d938b2cb0ccead4f75
Reintroduce uml_kmalloc for the benefit of UML libc code. The
previous tactic of declaring __kmalloc so it could be called directly
from the libc side of the house turned out to be getting too intimate
with slab, and it doesn't work with slob.
So, t
On Fri, Aug 01, 2008 at 06:41:25PM -0400, Jeff Dike wrote:
>From 94409ded7768e15b0d0a5a172d611073c72308de Mon Sep 17 00:00:00 2001
>
>Reintroduce uml_kmalloc for the benefit of UML libc code. The
>previous tactic of declaring __kmalloc so it could be called directly
>from the libc side of the hous
>From 94409ded7768e15b0d0a5a172d611073c72308de Mon Sep 17 00:00:00 2001
Reintroduce uml_kmalloc for the benefit of UML libc code. The
previous tactic of declaring __kmalloc so it could be called directly
from the libc side of the house turned out to be getting too intimate
with slab, and it doesn
