Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 13 Feb 2002 04:38:14 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 13 Feb 2002 04:38:05 -0500 Received: from pizda.ninka.net ([216.101.162.242]:63616 "EHLO pizda.ninka.net") by vger.kernel.org with ESMTP id ; Wed, 13 Feb 2002 04:37:46 -0500 Date: Wed, 13 Feb 2002 01:35:57 -0800 (PST) Message-Id: <20020213.013557.74564240.davem@redhat.com> To: alan@lxorguk.ukuu.org.uk Cc: akpm@zip.com.au, linux-kernel@vger.kernel.org, ralf@uni-koblenz.de Subject: Re: [patch] printk and dma_addr_t From: "David S. Miller" In-Reply-To: In-Reply-To: <3C6A2FCA.C4F49062@zip.com.au> X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org From: Alan Cox Date: Wed, 13 Feb 2002 09:40:44 +0000 (GMT) Vomit. How about adding a dma_addr_t %code to the printk function ? And gcc will discover this via what? Osmosis perhaps? :-) - 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/