From: "David S. Miller" <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
Date: Wed, 13 Feb 2002 03:36:41 -0800 (PST) [thread overview]
Message-ID: <20020213.033641.102576462.davem@redhat.com> (raw)
In-Reply-To: <E16awZq-0004s4-00@the-village.bc.nu>
In-Reply-To: <20020213.013557.74564240.davem@redhat.com> <E16awZq-0004s4-00@the-village.bc.nu>
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
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". :-)
next prev parent reply other threads:[~2002-02-13 11:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-13 9:20 [patch] printk and dma_addr_t Andrew Morton
2002-02-13 9:40 ` Alan Cox
2002-02-13 9:33 ` Andrew Morton
2002-02-13 9:34 ` Jeff Garzik
2002-02-13 9:38 ` Andrew Morton
2002-02-13 9:35 ` David S. Miller
2002-02-13 10:23 ` Alan Cox
2002-02-13 10:26 ` Andrew Morton
2002-02-15 21:37 ` Troy Benjegerdes
2002-02-15 21:51 ` David Woodhouse
2002-02-13 11:36 ` David S. Miller [this message]
2002-02-13 17:38 ` Richard Gooch
[not found] <0C01A29FBAE24448A792F5C68F5EA47D2172BC@nasdaq.ms.ensim.com>
2002-02-13 19:11 ` Paul Menage
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=20020213.033641.102576462.davem@redhat.com \
--to=davem@redhat.com \
--cc=akpm@zip.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=ralf@uni-koblenz.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox