Messages in this thread | | | Subject | Re: [BUG] vmalloc, kmalloc - 2.4.x | From | Grzegorz Jaskiewicz <> | Date | 03 Feb 2003 16:07:32 +0000 |
| |
On Mon, 2003-02-03 at 15:52, Russell King wrote: > 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)
Thx guys, i am concidering this as my lack of information. But anyway, i am really impressed in spead of response.
Chears :)
--
Grzegorz Jaskiewicz <gj@pointblue.com.pl> K4 Labs
- 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/
| |