Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 13 Feb 2002 06:38:58 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 13 Feb 2002 06:38:48 -0500 Received: from pizda.ninka.net ([216.101.162.242]:7042 "EHLO pizda.ninka.net") by vger.kernel.org with ESMTP id ; Wed, 13 Feb 2002 06:38:31 -0500 Date: Wed, 13 Feb 2002 03:36:41 -0800 (PST) Message-Id: <20020213.033641.102576462.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: <20020213.013557.74564240.davem@redhat.com> 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 10:23:50 +0000 (GMT) So how do they modify the printf format rules in gcc ? Because they can claim that they are part of the C environment, and for the most part they are right so their extensions go into gcc's magic list. In fact I'd claim their case to be plugging holes in the standards specified set of printf format strings. :-) Hey... we could "borrow" one of these printf format strings we don't have any need for in the kernel and pretend that is for "dma_addr_t". :-) - 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/