Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 3 Feb 2003 10:42:57 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 3 Feb 2003 10:42:57 -0500 Received: from caramon.arm.linux.org.uk ([212.18.232.186]:30990 "EHLO caramon.arm.linux.org.uk") by vger.kernel.org with ESMTP id ; Mon, 3 Feb 2003 10:42:57 -0500 Date: Mon, 3 Feb 2003 15:52:25 +0000 From: Russell King To: Grzegorz Jaskiewicz Cc: Linux Kernel Mailing List Subject: Re: [BUG] vmalloc, kmalloc - 2.4.x Message-ID: <20030203155225.A5968@flint.arm.linux.org.uk> Mail-Followup-To: Grzegorz Jaskiewicz , Linux Kernel Mailing List References: <1044285222.2396.14.camel@gregs> <1044285758.2527.8.camel@laptop.fenrus.com> <1044286926.2396.28.camel@gregs> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <1044286926.2396.28.camel@gregs>; from gj@pointblue.com.pl on Mon, Feb 03, 2003 at 03:42:06PM +0000 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 824 Lines: 25 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 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/