Messages in this thread | | | Date | Mon, 3 Feb 2003 15:52:25 +0000 | From | Russell King <> | Subject | Re: [BUG] vmalloc, kmalloc - 2.4.x |
| |
On Mon, Feb 03, 2003 at 03:42:06PM +0000, Grzegorz Jaskiewicz wrote: > > and that > > printk("<1>%d\n", TimerIntrpt); > > you shouldn't use <1> in printk strings ever. > <1>gives me messages on screen on my box, thats why. > > the same effect is while using kmalloc, just change vmalloc to kmalloc.
#include <linux/kernel.h>
and then use
printk(KERN_CRIT "%d\n", TimerIntrpt);
We have these definitions for a reason. 8)
-- Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux http://www.arm.linux.org.uk/personal/aboutme.html
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |