On Mon, 11 Feb 2008, Matt Mackall wrote:
> Can someone explain why the magic is needed (and preferably capture it
> in a comment somewhere sensible)? I took a peek at this and have no idea
> what's going on.
UML defined its own external __kmalloc and things. Isnt there some other
way to fix it? I guess including slab.h is not possible here?
/*
* Copyright (C) 2005 Paolo 'Blaisorblade' Giarrusso <[EMAIL PROTECTED]>
* Licensed under the GPL
*/
#ifndef __UM_MALLOC_H__
#define __UM_MALLOC_H__
#include "kern_constants.h"
extern void *__kmalloc(int size, int flags);
static inline void *kmalloc(int size, int flags)
{
return __kmalloc(size, flags);
}
extern void kfree(const void *ptr);
extern void *vmalloc(unsigned long size);
extern void vfree(void *ptr);
#endif /* __UM_MALLOC_H__ */
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
