From: Russell King <rmk@arm.linux.org.uk>
To: Grzegorz Jaskiewicz <gj@pointblue.com.pl>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] vmalloc, kmalloc - 2.4.x
Date: Mon, 3 Feb 2003 15:52:25 +0000 [thread overview]
Message-ID: <20030203155225.A5968@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1044286926.2396.28.camel@gregs>; from gj@pointblue.com.pl on Mon, Feb 03, 2003 at 03:42:06PM +0000
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
next prev parent reply other threads:[~2003-02-03 15:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-03 15:13 [BUG] vmalloc, kmalloc - 2.4.x Grzegorz Jaskiewicz
2003-02-03 15:19 ` Oliver Neukum
2003-02-03 15:19 ` Arjan van de Ven
2003-02-03 15:35 ` Grzegorz Jaskiewicz
2003-02-03 15:35 ` Arjan van de Ven
2003-02-03 22:52 ` David Woodhouse
2003-02-03 15:22 ` Arjan van de Ven
2003-02-03 15:42 ` Grzegorz Jaskiewicz
2003-02-03 15:52 ` Russell King [this message]
2003-02-03 15:58 ` Arnaldo Carvalho de Melo
2003-02-03 16:07 ` Grzegorz Jaskiewicz
2003-02-03 15:39 ` Richard B. Johnson
[not found] <1044284924.2402.12.camel@gregs>
[not found] ` <1044289102.21009.1.camel@irongate.swansea.linux.org.uk>
2003-02-03 15:40 ` Grzegorz Jaskiewicz
2003-02-03 15:40 ` Grzegorz Jaskiewicz
2003-02-03 17:02 ` Benjamin Herrenschmidt
2003-02-03 17:18 ` Alan Cox
2003-02-03 22:54 ` David Woodhouse
2003-02-04 9:35 ` Arjan van de Ven
2003-02-04 12:33 ` Dave Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030203155225.A5968@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=gj@pointblue.com.pl \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.